Re: Handle HTTP error 511 Network Authentication Required (standard secure proxy authentification/captive portal detection)
- From
Daniel Stenberg <daniel@haxx.se>
- Date
- Feb 20, 2012, 19:06 UTC
- Message-ID
- <alpine.DEB.2.00.1202202002330.28090@tvnag.unkk.fr>
- In-Reply-To
- <20120220154452.GA27456@sigill.intra.peff.net>
On Mon, 20 Feb 2012, Jeff King wrote:
Show 6 quoted lines
> 3. Open a browser and say "Ah, I see. A captive portal". > > We should already be doing that. Adding more support could make step 3 a > little nicer, but like I said, I'd be more interested in seeing a real case > first. It may even be a feature that would be more appropriate to curl > (which git builds on for http access).
We're already discussing the 511 in the curl camp as well, but with even more sighs and hands in the air. 511 is clearly intended for HTML-understanding user agents and curl is not one of those. IMHO, curl will remain to simply help users to figure out that it is 511 and leave it at that.
As a git user, I would probably be very surprised if using 'git' suddenly caused by browser to pop up a captive portal login. I would prefer git to instead properly explain to me that is being the victim of a 511 and what I should do to fix it.
-- / daniel.haxx.se