Scheduled maintenance is currently in progress. We will provide updates as necessary.
Posted Nov 12, 2018 - 22:00 CET
Scheduled
Shadow launch of the ability to forward request to the origin through existing machine
To be more flexible regarding the addition of node, we will forward request to the origin through existing machine. This will be activated on new machines only.
Shadow launch of the ability to directly send request to the cache without using the front layer
This will reduce the bandwidth consumed on the front layer. This will not be activated for the moment.
Prepare addition of new machine without updating the IP lists
To be more flexible regarding the addition of node, we will forward request to the origin through existing machine. This will be activated on new machines only.
Monitor keycdn error ratio
As indicated in our last post-mortem, we improve the monitoring of errors introduced by our platform.
The engine migrate to node 8.
We migrated our engine to the last LTS version. This migration was a long due on our side. Most of the work has been done during this summer and this version has already been validated on a portion of our platform.
Don't add a Cache-Control header based on the last-modified header
When the Cache-Control header is not present on the response but a Last-Modified header is present, the spec allows to compute a TTL (generally browsers implement 10% of the duration since the last update. This is now removed since we encounter website setting a Last-Modified header on page that must not be cached.
Reduce congestion in the Front layer
We were using the front layer to send internal requests to the cache layer. This is now removed and the cache layer is addressed directly. This reduces potential bandwidth congestion on the front layer.
Brotli is supported at the origin
We correctly decode origin response using the Brotli compression algorithm.
Fix discovery mode
In discovery mode, when optimizations were enabled by the plugin, it was possible that some cache rules were not applied.
Support Protocol Rewriting
It's now possible to rewrite the page with HTTPS links even if the received request is in HTTP. This is particularly important when a CDN in front of Fasterize modify the protocol.
Posted Nov 09, 2018 - 11:10 CET
This scheduled maintenance affected: API, Dashboard, Acceleration, Website, Logs delivery, and Collect.