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
Yes there is a problem: If the Content-Encoding is set to "none" then the module does still assume that the response is compressed.
I understand that the header is non-standard (https://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.11), however it seems to be needed in some special cases. I'm currently testing that, however and for the time being, I think that ignoring "none" wouldn't hurt...
See also getgrav/grav#548
Hi. Thanks a lot for your work, it's very valuable. Since compressed responses are a vast majority, are there plans to enable substitution module to work on compressed responses?.
2014/05/09 13:28:50 [warn] 19808#0: *312 http subs filter header ignored, this may be a compressed response. while reading response header from upstream, client: xx.xx.xx.xx, server: , request: "GET / HTTP/1.1", upstream: "http://194.71.107.80:80/", host: "tpb.rtbt.me", referrer: "http://tpb.rtbt.me/top/101"
The text was updated successfully, but these errors were encountered: