GZIP decoding error

[chdh]

I have written a test program to reproduce the GZIP decoding problem.

See: #907, #912, Chromium bug 801237

To run the test program:

• Install Node (download from https://nodejs.org).
• Start the test program with the following command:
  node dist/main.js
• Open the browser at http://localhost:8080
• Enter any user name and password at the prompt.
• Now the error occurs: GZIP encoded data is displayed within the content area of the browser.
• Reload the page with F5. The page loads correctly.

Notes:

• The error does not occur with content type "text/plain" instead of "text/html". When content type is "text/plain", the browser makes a second HTTP request.
• The error does not occur when both the callenge response and the final response are compressed. I guess that the "Content-Encoding" value of the challenge response is used to decode the final response.
• The error does not occur when disableCSPReportInjection is set to true in the uMatrix options. I guess that when disableCSPReportInjection is false, header fields of the challenge response are modified and applied for processing the final response.
• The test program is written in TypeScript, but the compiled JavaScript program is included, so that you don't need the TypeScript compiler.

testHttpServer.zip

[gorhill]

Why open an issue which you know to be a duplicate? (and also known to be a browser issue?)

uMatrix does not deal with response body data, there is no extensions API in Chromium to do so -- this is a browser issue, there is nothing I can do aside offering a workaround which seems to trigger less the browser issue.

[chdh]

I opened a new issue because #907 was closed and #912 is locked and maybe for something different, but has the label "unable to reproduce".

I thought you would be happy to receive a well documented test case to reproduce the problem, but I get the feeling, that my contribution is not welcome here. And on the Chromium bugs site, nobody reacted to my last 2 posts.

[gorhill]

I locked because of the unproductive comment:

Why do you suggest that this is a Chrome problem and not your plugin

Now:

I get the feeling, that my contribution is not welcome here

It's a browser issue, there is nothing I can do (aside the already available and documented workaround), I already said so in the other issue.