No Content-Encoding added when loading .gz files #190
Replies: 2 comments 4 replies
-
Did you read the doc also ? Or look at other existing projects ? |
Beta Was this translation helpful? Give feedback.
-
Guys, i got it. Here's my explanation with a static route example:
Lets say we have a static route for directory called X:/FOLDER1/. And therefore pointless for gzip-compressed content if the gzip-compressed file is somewhere INSIDE /FOLDER1/, because this specific header isn't set for decompression: I don't know why but this header won't be added somehow. So i moved the static route to another directory and my compressed file in another test directory:
All not compressed files: All compressed files: Everything in Folder It works. ! :D Now i check in
Maybe not perfect, but I'm tired now and I'm calling it a day. :> |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I've been trying for days to get it to load and process gz-compressed files, but it just doesn't work because of the missing content encoding header.
(ChatGPT is useless too; it just produces garbage in that case.)
I've read here (me-no-dev#556) that the Content header is supposedly set automatically, but that's somehow not true.
My gz files don't receive this header from the web server.
I use a static route
This doesn't work with gz-compressed files.
Then i tried several methods like this:
But this also doesn't work.
The browser loads it as a normal file, and there's no content encoding in the response.
See here:
Please tell me what else I should do. :')
Edit: I'm using the actual 3.7.7 library.
Beta Was this translation helpful? Give feedback.
All reactions