API and dashboard have been updated successfully. We postponed the deployment of the engine because of an instability discovered during the canary phase. A new date will be communicated for the engine update.
Posted 3 months ago. Oct 25, 2018 - 01:49 CEST
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Posted 3 months ago. Oct 24, 2018 - 22:30 CEST
The deployment is postponed on Wednesday, October 24. We need to verify an anomaly in our continuous integration that may affect our automatic deployment.
Posted 3 months ago. Oct 22, 2018 - 19:16 CEST
The engine and our API code 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.
Fix on the dashboard in the domain section
A user was able to remove the origin from the configuration when submitting change via the keyboard
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 3 months ago. Oct 19, 2018 - 09:15 CEST
This scheduled maintenance affected: API, Dashboard, Acceleration, Website, Collect, and Logs delivery.