Closed
Bug 191677
Opened 22 years ago
Closed 9 years ago
WC3 CUAP: Remember traverse redirects
Categories
(Core :: Networking, enhancement)
Core
Networking
Tracking
()
RESOLVED
FIXED
People
(Reporter: gerv, Unassigned)
References
()
Details
[ This bug is one of the recommendations in the W3C's "Common User Agent
Problems" document, URL above. One bug has been filed on each recommendation,
for deciding whether we do it and, if not, whether we should. ]
1.15 Remember traverse redirects
When the browser traverses a redirect, it should remember both the original
URI and the target URI for marking links as visited.
Is there a test case that shows we have incorrect behavior?
Is this specific to HTTP or could it apply to other protocols?
Reporter | ||
Comment 2•22 years ago
|
||
Presumably it also applies to HTTPS; but I don't know of any other protocol
which provides redirects.
We don't necessarily have incorrect behaviour - "One bug has been filed on each
recommendation, for deciding whether we do it and, if not, whether we should."
If someone writes a quick test case and shows we do this right, we can resolve
this bug.
Gerv
Comment 4•22 years ago
|
||
this may actually be something for the docshell/docloader to solve. the
docloader incepts redirect notifications from necko, and it could/should
probably forward that information to global history somehow.
Severity: normal → enhancement
Target Milestone: --- → Future
Updated•19 years ago
|
Assignee: darin → nobody
QA Contact: benc → networking
Target Milestone: Future → ---
Comment 5•9 years ago
|
||
loadinfo carries this info now
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•