HTTP/2.0 200 OK
Date: Thu, 12 Sep 2019 19:38:24 GMT
Last-Modified: Tue, 07 Dec 2010 23:35:04 GMT
I solved the problem temporally adding the “not” pointing to
Is this a bug or is there something missing in my Caddyfile?
Thank you for your help.
Hi @enrique-quinteros, welcome to the Caddy community.
What’s your full Caddyfile?
There might be something there that’s writing the response and not specifying the content type.
Within the gzip handler code there is a comment noting specifically that if the underlying handler does not write a
Content-Type, some browsers will assume a content type of
application/x-gzip and try to download the file. The gzip handler even attempts to detect the content type (using the Golang http standard library functions) in this event, to try and prevent this.
I will let you know.
Thank you for your reply.
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.