Bug 795170 - Handle HTTP error 511 Network Authentication Required (standard secure proxy authentification/captive portal detection)
Summary: Handle HTTP error 511 Network Authentication Required (standard secure proxy ...
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora
Classification: Fedora
Component: firefox
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Gecko Maintainer
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-02-19 21:46 UTC by Nicolas Mailhot
Modified: 2012-03-27 14:04 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-03-27 14:04:04 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Mozilla Foundation 728658 0 None None None Never

Description Nicolas Mailhot 2012-02-19 21:46:15 UTC
Since
http://code.google.com/p/chromium/issues/detail?id=7338 and
https://bugzilla.mozilla.org/show_bug.cgi?id=479880

there was no clean way for a proxy or captive portal to get a web client to
display an authentication dialog when user credentials expire while he is
browsing on an https url.

The IETF finally set up to fix this problem and defined a standard HTTP error
that lets access control equipments tell the web client authentication or
re-authentication is needed and where the authentication form is located.

http://tools.ietf.org/id/draft-nottingham-http-new-status-04.txt

→ <http://www.rfc-editor.org/queue2.html#draft-nottingham-http-new-status>
(the spec is approved and in the queue for publication as RFC)

Please add error 511 handling in Fedora Firefox, so Fedora desktops can be used on corporate networks that implement HTTP error 511 as proxy authentication method

Comment 1 Jan Horak 2012-03-27 14:04:04 UTC
Thanks for report and escalation to upstream too, we're going to track this issue on Mozilla mozbz#728658.


Note You need to log in before you can comment on or make changes to this bug.