- From: <bugzilla@jessica.w3.org>
- Date: Thu, 26 Sep 2013 02:24:45 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=12607
Gili <cowwoc@bbs.darktech.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |cowwoc@bbs.darktech.org
--- Comment #9 from Gili <cowwoc@bbs.darktech.org> ---
I have a proposal that is similar to one originally brought up on the mailing
list, but a bit different (I suspect Mozilla's implementation already works
this way). Instead of adding a "followRedirects" flag and forcing users to
issue new requests at each "redirect hop", add a "redirect observer" as
follows:
1. Allow users to register an event listener.
2. Every time the server returns a response, the event listener is fired with
the response body and headers.
3. At this point, the listener may allow the request to continue or terminate
it.
4. If the listener terminated the request, set readyState to some value that
indicates the process was "terminated by the user".
5. If the listener allows the request to continue and the response required a
redirect, issue the new request and go to step #2.
6. Eventually no more redirects occur, and readyState is set to DONE as usual.
This would have the nice side-effect of addressing bug #23361 which I just
filed.
Does this address everyone's use-cases?
I read the mailing list posts at
http://lists.w3.org/Archives/Public/public-webapps/2010JulSep/thread.html#msg474
but it wasn't clear why "followRedirects" ended up being removed from the
standard. Anne, could you shed some light?
--
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Thursday, 26 September 2013 02:24:46 UTC