Learn about new features, enhancements, known issues, resolved issues, and other important details for Rackspace CDN API 1.0 service in the following release note information.
For information about using the API, see the documentation overview.
Validation added to top level domains during secure certificate requests.
Retries a different DNS shard if the shard is at capacity.
Fixed the ordering of caching rules in terms of restrictiveness, causing some rules to not apply.
Fixed an issue where adding a second domain to your service caused log delivery to be disabled.
Fixed the duplicate mapping of the country code for Costa Rica in the geographical restrictions.
The access URL now appears when a service with SAN is created instead of waiting until after the SAN cert is deployed.
Fixed an issue to submit the Akamai product information when requesting a SAN certificate, which resolves a problem where SAN certificate requests have been failing.
For the API, fixed Guyana’s country code. This issue was causing geographical restrictions to fail in some cases.
For the API, added a better validation message for blacklisting and whitelisting geographies.
In the Cloud Control Panel for Rackspace CDN, fixed an issue where the text that describes the time to deploy a SAN certificate needed more clarification when users are requesting a SAN certificate.
In the Cloud Control Panel for Rackspace CDN, fixed an issue where the example domain in the text box was not a subdomain, which caused confusion to users.
The delete an SSL certificate operation has been added.
WARNING: If you delete a working SSL certificate, you will break your CDN service.
In the Control Panel, customers can now create and edit CDN services using domains with SAN certificates without going through Rackspace Support.
In the Control Panel, the layout of the Service Details page has been changed to better display domains and associated Transport Layer Security (TLS) certificates.
For the API, the certificate status is now returned in the JSON of HTTPS domains.
For the API, fixed an issue where new domains appeared to be already taken.
Rackspace CDN now supports Classless Inter-Domain Routing (CIDR) for both IPv4 and IPv6. See the create service operation.
Added CIDR support in the create service operation for IP address restrictions.
The default value for the
hard query parameter in the
purge a cached asset operation has been
true, which indicates a purge.
geographyparameter has been added to
restrictionsfor the create a service operation. You can use this parameter to specify a country from which you want to restrict requests.
IP restrictions now support IPv6 addresses for the create a service operation.
Cache invalidation has been added to the purge a cached asset operation through the
hardquery parameter. The default value for
hardis set to
false, which does cache invalidation, while setting the value to
trueperforms an actual purge.
accessattribute with valid values of
blacklisthas been added to the
restrictionsparameter for the create a service operation to allow or block access.
client_ipattributes have been added to the
rulesparameter for the create a service operation. These attributes enable restriction rules for URLs and IP addresses.
New services are now created with a default TTL for
/*. You see this default TTL in the
rulessection of the service.
Fixed an issue to now disallow entering a root domain for the domain field in a service
Fixed an issue where now a TTL of 0 seconds is treated as “no-cache” with Akamai
Rackspace CDN has been updated to include host header information by
hostheadervalue parameters to
the create a service request.
Rackspace CDN has been updated to allow HTTP traffic on an SSL
domain. Consequently, the description of the
protocol parameter for
the request in the create a service operation
has been changed. The statement that indicated that domains must use the same
protocol has been deleted.
This is the initial Unlimited Access (UA) release of the Rackspace CDN API.