web.archive.org produces ERR_CONNECTION_CLOSED, but works in private tab

[brianddk]

Description

Possible cache corruption. When visiting https://web.archive.org I get an ERR_CONNECTION_CLOSED error, but it goes away if I clear my cache or try in a private tab.

Steps to Reproduce

1. Browse to https://archive.org
2. Click 'Web' icon on main page
3. Redirect to https://archive.org/web/
4. Enter https://github.com/brave/brave-browser/ in the save dialog
5. Click "save" (submit)
6. Redirect to https://web.archive.org/save/https://github.com/brave/brave-browser/
7. Observe ERR_CONNECTION_CLOSED

Actual result:

Expected result:

Expect the cache for web.archive.org to work and not require a clear to function.

Reproduces how often:

Reproduces whenever I open a url to web.archive.org

Brave version (brave://version info)

• Brave 0.64.77 Chromium: 74.0.3729.169 (Official Build) (64-bit)
• Revision 78e4f8db3ce38f6c26cf56eed7ae9b331fc67ada-refs/branch-heads/3729@{Extensions installed from should have a generic name #1013}

Version/Channel Information:

• Can you reproduce this issue with the current release? Yes
• Can you reproduce this issue with the beta channel? No
• Can you reproduce this issue with the dev channel? No
• Can you reproduce this issue with the nightly channel? Unknown

Other Additional Information:

• Does the issue resolve itself when disabling Brave Shields? No
• Does the issue resolve itself when disabling Brave Rewards? No
• Is the issue reproducible on the latest version of Chrome? No

Miscellaneous Information:

I suspect it cannot reproduce on Chrome, brave-beta, and brave-dev, simply because the contents of the cache is different. Once the cache for web.archive.org corrupts, it stays corrupted until I clear cache.

[brianddk]

Reddit thread

[brianddk]

I found out how to reproduce it. The error arises on roaming proxies. Let me explain. Where I work we have a number networks. One of them is highly secured and requires all traffic to go through a proxy (which is slow). The proxy is only accessible on the network that it is required on, but all browsers (brave, chrome, firefox) will revert to no-proxy when the named proxy NACKs. Problem is... waiting for the NACK slows things down, so when I'm off that network, I usually go into windows proxy settings and clear the proxy address.

This is what corrupts the Brave cache. Loading a page through my proxy once, then going to it again when my proxy NACKs kills that page. Only way around it is to do a global nuke on the cache, or to re-enable the proxy (which NACKs) and just deal with the delay.

[d-Rickyy-b]

The same issue happens for me in Firefox, Chrome, Brave and Edge. I cannot access the subdomain web.archive.org at all. From my phone in the same network using Firefox/Chrome/Brave it works perfectly fine. This looks like a bigger issue to me.

EDIT: I am not using any kind of proxy btw.