On Wed, 07 Oct 2009 02:48:37 +0200, Henrik Nordstrom
<hen...@henriknordstrom.net> wrote:
> ons 2009-10-07 klockan 13:09 +1300 skrev Amos Jeffries:
> 
>> 3.0 uses a generic fail() mechanism to send results back. That mechanism
>> seems not to add the Proxy-Auth reply header at all. 3.0 also was only
>> parsing the URL and config file. Popup re-sends contain the auth in
>> headers
>> not URL.
> 
> Strange. My 3.0 responds as
> 
> HTTP/1.0 401 Unauthorized
> Server: squid/3.0.STABLE19-BZR
> X-Squid-Error: ERR_CACHE_ACCESS_DENIED 0
> WWW-Authenticate: Basic realm="ftp username"
> 
> and relays Authorization properly. It however rejects any login other
> than the one supplied in the URL.
> 
> Squid-2 behaves the same.

Ah, okay. So the reply header must have been 3.1 specific then. The request
header checking was both.

Might be possible to fix it by porting the new checkAuth() function alone.

Amos

Reply via email to