Open wknapik opened 2 years ago
The upstream issue was closed as a WontFix, because it's a site issue (which it is). Here's my comment from the chromium tracker:
This is a site issue, but the user is navigating to a valid url, that returns 200 and a browser setting is causing them to see 404. This sort of site misconfiguration may be common and it is detectable. The browser could behave differently when the https url returns an error and the http url doesn't. The user may be presented with a choice of what to do for instance.
Do we take the same approach as upstream, or do something else?
Description
The article at http://wroclawskiejedzenie.pl/2022/03/07/polacy-jestescie-wspaniali-niech-rzad-nie-przypisuje-sobie-waszych-zaslug/ is present, but in http-nowhere mode I'm getting redirected to https and getting a 404.
Steps to Reproduce
Always use secure connections
Actual result:
404
Expected result:
200
Reproduces how often:
Easily reproduced
Brave version (brave://version info)
Version/Channel Information:
Other Additional Information:
Miscellaneous Information:
We can use this issue for other examples of site breakage