-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Missing HTTP Response Header "Content-Encoding: gzip" #780
Comments
Did a little investigating, the issue is in this block of code shown below, the test for file === gzippedFile always fails. I replaced the test with if (file.includes(".gz")) and it works correctly for me now. This is just a hack and probably not the intended way things should work but it gets it done for now. cheers.
|
Just a little added thought. Perhaps the script checks for a regular file and then sees if there is also a .gz file version of the same file? In my case there is only a .gz file, no regular file exists. So I think it is attempting to see if there is a .gz.gz file which of course will fail, when in fact it should just serve the .gz file without checking if there is a gz and a non-gz file. |
This issue has been inactive for 180 days |
Thanks! |
Bump. |
I've started a pull request but it probably still needs some work |
Bump. |
-g option will enable content-type: application/gzip; charset=utf-8
but this is not enough, it has to have "Content-Encoding: gzip" also in response header
here is an example of error message when attempting to serve gzip content:
The text was updated successfully, but these errors were encountered: