Wayback Machine returning network protocol error
Categories
(Core :: Networking, defect, P3)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox66 | --- | fix-optional |
| firefox67 | --- | fix-optional |
| firefox68 | --- | fix-optional |
People
(Reporter: lizzard, Unassigned)
References
Details
(Keywords: regression, regressionwindow-wanted, Whiteboard: [necko-triaged])
Attachments
(1 file)
|
1.39 MB,
text/plain
|
Details |
Putting a url into the Wayback Machine (https://archive.org/web/) takes you to a url constructed like this: https://web.archive.org/web/*/https://gordonhuether.com/bart-station-san-bruno
This works in Chrome but not in Firefox. The regression must be fairly recent - it works in 66.0b9 but not in 67 nightly.
Comment 1•7 years ago
|
||
The URL seems to work in my windows 67 nightly build built from https://hg.mozilla.org/mozilla-central/rev/6924dd16f7b1e2e6ce71a8eb4cbe330d3e4745dc
Comment 2•7 years ago
|
||
WFM in Mozilla/5.0 (X11; Linux x86_64; rv:67.0) Gecko/20100101 Firefox/67.0 ID:20190225102402, Liz do you still experience this bug?
Comment 3•7 years ago
|
||
Tried to reproduce on latest Nightly 67.0a1 20190225102402, also on 20190223041557 x32 and 20190223041557 x64 on Win10, but couldn't.
Liz, were you using a specific OS when you had encountered this issue? Is the issue still reproducible on your side?
| Reporter | ||
Comment 4•7 years ago
|
||
MacOS 10.14.3. Yes, still reproducible in the latest nightly.
Comment 5•7 years ago
|
||
I still didn't manage to reproduce the issue, though I've also tried on a MacBook Pro with recent update to 10.14.3.
I've tried on 67.0a1 20190225215823 and 20190225102402 with the following steps:
*Navigated to archive.org/ using a fresh profile
*Manually added and searched for https://gordonhuether.com/bart-station-san-bruno
*Direct access from URL bar to the https://web.archive.org/web/*/https://gordonhuether.com/bart-station-san-bruno
In both cases the page opened correctly without any errors, though indeed at the first try it seemed to take longer for the page to load.
I was trying on a wireless connection on macOS v10.14.3, v.10.14.2 and a wired connection on v.10.14.
Comment 6•7 years ago
|
||
WFM too.
Hello Liz,
Could you attach the log and append the "Current Log Modules:" with nsStandardURL:5
See instructions here: https://developer.mozilla.org/en-US/docs/Mozilla/Debugging/HTTP_logging
| Reporter | ||
Comment 7•7 years ago
|
||
| Reporter | ||
Comment 8•7 years ago
|
||
Hi Junior, does this help? I pulled out just everything to do with archive.org in the log.
Comment 10•7 years ago
|
||
Oops, it seems you filter the log with archive.org only.
Could you attach the full log without censoring.
If privacy matters, maybe start with a clean profile (we can also check if it's by extension or not)
OR send a private mail to me?
Thanks!
| Reporter | ||
Comment 11•7 years ago
|
||
I'll try to do this soon, good point that I should try without extensions.
Updated•7 years ago
|
Comment 12•7 years ago
|
||
I could be a dup of bug 1528317.
Comment 13•7 years ago
|
||
(In reply to Junior [:junior] from comment #12)
I could be a dup of bug 1528317.
It would seem so.
| Reporter | ||
Updated•7 years ago
|
| Reporter | ||
Updated•7 years ago
|
| Reporter | ||
Updated•7 years ago
|
| Reporter | ||
Comment 15•7 years ago
|
||
Just tested this out on the current Nightly with the fix from bug 1528317. Rather than seeing the network protocol error, the submission to archive.org no longer gives any result. So, a different error, but the issue is not resolved.
| Reporter | ||
Updated•7 years ago
|
Comment 16•6 years ago
|
||
Cross reference:
– under Firefox not loading https://web.archive.org/ – about:newtab or about:blank in lieu of content
Re: https://pastebin.com/P59YsVud (troubleshooting information) lines 841–923, might a modified preference be the cause and if so, which one(s)?
TIA
Comment 17•6 years ago
|
||
Now I see:
- https://web.archive.org/ pages that will not load in normal windows do load in private windows.
Please: what next to diagnose the cause?
Comment 18•6 years ago
|
||
I guess that Manage Data… is somehow unreliable in (at least) Firefox 71 and 72.
tl;dr the Internet Archive pages began working after removing cookies; cookies that Firefox apparently silently failed to remove.
Description
•