W3C home > Mailing lists > Public > public-webapps-bugzilla@w3.org > November 2012

[Bug 15418] sort out HTTP auth

From: <bugzilla@jessica.w3.org>
Date: Sat, 24 Nov 2012 08:55:13 +0000
To: public-webapps-bugzilla@w3.org
Message-ID: <bug-15418-2532-NYTE0N4roq@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=15418

--- Comment #10 from Anne <annevk@annevk.nl> ---
So I think if we let this get handled by Fetch it will include the
Authorization header on the first try and then either you will get a 200 or a
403. If you do not include it you might get a 401 and URL's username/password
will be used. I suspect we should let Fetch handle 401's automatically in that
case and otherwise defer to UI (though more testing is needed for
<script>/<img>/...).

(At some point we might want to offer a way in which 401 gets back to
XMLHttpRequest without the UA trying do do smart things. Same with redirects.)

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Saturday, 24 November 2012 08:55:18 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Saturday, 24 November 2012 08:55:20 GMT