gorhill / uMatrix

uMatrix: Point and click matrix to filter net requests according to source, destination and type
GNU General Public License v3.0
4.55k stars 470 forks source link

Mishmash chars on page after login via "WWW-Authenticate: Basic realm" (chrome) #907

Closed Monter closed 6 years ago

Monter commented 6 years ago

On websites with logging in using the "WWW-Authenticate: Basic realm" method, after logging in, the page displays a mix of characters. To display the correct content you need to refresh the page. The problem occurs in a plug-in that is newer than version 1.2.0.

gorhill commented 6 years ago

Closing and marking as invalid, as per CONTRIBUTING.

Monter commented 6 years ago

I can not paste my website here, its address or screenshots because I did not protect it from access to show what is on it. To repeat the problem add the header "WWW-Authenticate: Basic realm" to any PHP page, and the request for login and password - when you enter it, the page will open, but instead of the content will be random characters. After refreshing F5, the content is already correct. All new versions have this problem, v1.1.20 works correctly.

Everywhere you write that you do not have time. If you do not have it, do not make new versions with errors.

gorhill commented 6 years ago

I need reproducible steps. Yours are quite demanding -- I need top setup a web server. Since you can reproduce on your side, best would be you investigate the issue. It's not necessarily uMatrix, you should test with other extensions which also modify the sent and received headers -- this could show that the issue is not specific to uMatrix. Bottom line, please contribute by investigating further the issue you see.

There are other problems with your issue, for example you did not provide browser info, or look at the logger, or provide some analysis as to the provenance of those "mishmash chars". In the end because of the lack of investigation on your side, I closed as invalid.

chdh commented 6 years ago

The error only occurs when the authentication challenge response (with status code 401 and "WWW-Authenticate" header field) is uncompressed and the final response is compressed.

There is a Chromium bug entry for the same problem.