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
I'm trying to serve compressed versions of my HTML files. I've added the -g flag and I see Serve GZIP Files: true during startup. I've zipped a test file using gzip.
When I try to access the file without the .gz extension I get a 404
When I access the file with .gz I get the gzipped file
When I copy the unzipped file and try to access that I am served the unzipped file (no Content-Encoding response header) - although for the screenshot I simply copied the compressed file without .gz extension.
As you can see in the screenshot the request header contains Accept-Encoding: gzip.
I'm basically seeing this issue but I'm on version 14.1.1
Update: I manually ran fs.stat and hasGzipId12 in an interactive node session on the server (from within docker) and neither fails. !gzipErr is true and isGzip is also true. So I can only assume that something goes wrong before it even gets to that code.
I'm trying to serve compressed versions of my HTML files. I've added the
-g
flag and I seeServe GZIP Files: true
during startup. I've zipped a test file using gzip..gz
extension I get a 404.gz
I get the gzipped file.gz
extension.As you can see in the screenshot the request header contains
Accept-Encoding: gzip
.I'm basically seeing this issue but I'm on version 14.1.1
Environment Versions
Steps to reproduce
Run http-server with
-g
flag and try to access a file (without.gz
extension) for which a.gz
version is available.Expected result
The gzipped file is being served and decompressed client side.
Actual result
404 when trying to access the file without
.gz
extension.The text was updated successfully, but these errors were encountered: