Closed
Bug 1310437
Opened 8 years ago
Closed 8 years ago
No redirect limit in case of closed loop using window.location.href
Categories
(Core :: DOM: Core & HTML, defect, P3)
Tracking
()
RESOLVED
INVALID
People
(Reporter: cs.anurag.jain, Unassigned)
Details
Attachments
(1 file)
372 bytes,
application/zip
|
Details |
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2785.143 Safari/537.36
Steps to reproduce:
1) Download & extract bug.zip from attachment. Place a.html and b.html in one directory
2) Open a.html using firefox
3) It will go into an infinite loop.
Actual results:
Infinite & endless loop was observed. There was no redirect limit which could stop this redirection.
Memory and CPU overutilization
Expected results:
User should be presented with an alert popup asking if wants to prevent site from creating further redirects.
Comment 1•8 years ago
|
||
We behave the same as Safari and Chrome. Do you have any comment about how we want to enhance this? Thanks.
Flags: needinfo?(bugs)
Priority: -- → P3
Comment 2•8 years ago
|
||
I don't know why or how we could really change the behavior here.
One could always add some timeout and load a new page. And this isn't really different to location.reload()
Reporter, if you think there should be some limit, please file an HTML specification bug explaining why and how you think this should work. Thanks.
https://github.com/whatwg/html/issues
Status: UNCONFIRMED → RESOLVED
Closed: 8 years ago
Flags: needinfo?(bugs)
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•