We decided to postpone the maintenance to give time for the current investigation about the slowdown that appear today. We will reschedule another maintenance window.
Posted 5 months ago. Oct 29, 2018 - 19:16 CET
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.
Fix edge cases on origin update
There was a bug on updates that modify the type of the DNS record (for instance, the replacement of a domain name by an IP address). and we now completely support IPv6 address at the origin
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 5 months ago. Oct 26, 2018 - 15:37 CEST
This scheduled maintenance affected: Acceleration.