- 22 Oct 2024
- 1 Minute to read
- Print
- PDF
August 2024 Release
- Updated on 22 Oct 2024
- 1 Minute to read
- Print
- PDF
Highlights
- Extended HTTP Response Codes for Origin Error Caching
- New Delivery Reports API Endpoint
Extended HTTP Response Codes for Origin Error Caching
Error caching allows for configurable behavior of the CDN and the requesting client, when an error code is returned from Origin.
Qwilt’s Origin Error Caching has now been enhanced with additional response codes, with all HTTP response codes supported except 200,206,204,301,302,304, and 307.
Values can be set to:
- An integer representing time in seconds
- Obey origin
- No-store - which will not cache the error, or
- No-cache - which forces revalidation with the origin before serving the cached error.
New Delivery Reports API Endpoint
A new Delivery Reports API endpoint, reports.cqloud.com/api/3/reports/cp/aggregation/ is replacing the old version (api/2). The new version offers enhanced functionality, including the ability to filter by descriptive text for properties - such as siteName, CP, and ISP.
When transitioning to the new endpoint, your existing internal filter names will still function, but the response will be formatted with descriptive text.
The previous API version (api/2) will be deprecated by March 31, 2025. Within this period of time, you will need to update your GET requests and adjust your code to accommodate the new names format in the API response.
For additional information, see the Delivery Reports section of our API documentation.
For additional information about any of the above features or resolved issues, contact support@qwilt.com.