Closed
Bug 1225593
Opened 10 years ago
Closed 10 years ago
Break 301 Redirect Loop by invalidating cache
Categories
(Core :: Networking, enhancement)
Tracking
()
RESOLVED
DUPLICATE
of bug 696646
People
(Reporter: james2432, Unassigned)
Details
Attachments
(1 file)
|
95.07 KB,
image/jpeg
|
Details |
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:45.0) Gecko/20100101 Firefox/45.0
Build ID: 20151116030208
Steps to reproduce:
1. Had a website the returned a 301 permanent to https:// version
2. https:// version broke things and had to revert to http://
3. Added 301 permanent to http:// and removed 301 to https://
Actual results:
Cache detected it has visited website in the past, so it redirects to https:// the https:// has a 301 to http:// it redirects to that. The cache tells firefox to redirect to https:// and the vicious cycle commences
Expected results:
Firefox could detect that there is a 301 cycle happening to the same URI (http vs https) and invalidate the cache
Updated•10 years ago
|
Severity: normal → enhancement
Status: UNCONFIRMED → NEW
Component: Untriaged → Networking
Ever confirmed: true
Product: Firefox → Core
Summary: 301 Redirect Loop → Break 301 Redirect Loop by invalidating cache
Updated•10 years ago
|
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•