You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 1, 2023. It is now read-only.
Context
I am running a react app and am trying to serve gzip compressed files (ideally pre-compressed during build time).
I am using those two buildpacks :
heroku/nodejs
heroku-buildpack-static: it is said in the doc that on the fly gzip compression is included by default (not gzip_static unfortunately), which is the case when you check the Nginx template file
What is happening
From the browser side, a query with Accept-Encoding: gzip, deflate, br is included.
However the file served are not compressed on the fly (no size change, no gzip encoded in header response.
Have any of you managed to get gzip compression work ? Would you have any idea what I am doing wrong?
In the docs, it is mentioned to In case you have multiple buildpacks for the application you can ensure static rendering in Procfile with web: bin/boot.
Thanks a lot for your help 😀
The text was updated successfully, but these errors were encountered:
chrisbag
changed the title
Serving GZIP files
Nginx Serving GZIP files
Apr 12, 2022
Context
I am running a react app and am trying to serve gzip compressed files (ideally pre-compressed during build time).
I am using those two buildpacks :
What is happening
From the browser side, a query with
Accept-Encoding: gzip, deflate, br
is included.However the file served are not compressed on the fly (no size change, no gzip encoded in header response.
Have any of you managed to get gzip compression work ? Would you have any idea what I am doing wrong?
In the docs, it is mentioned to
In case you have multiple buildpacks for the application you can ensure static rendering in Procfile with web: bin/boot.
Thanks a lot for your help 😀
The text was updated successfully, but these errors were encountered: