lör 2006-06-24 klockan 20:51 -0700 skrev Merton Campbell Crockett:
> In this instance, Squid received an HTTP/1.1 response from the IIS
> 6.x server with a status of 401. Included in the HTTP response
> header were the following fields.
>
> WWW-Authenticate: Negotiate
> WWW-Authe
On 24 Jun 2006, at 18:47 , Henrik Nordstrom wrote:
lör 2006-06-24 klockan 16:25 -0700 skrev Merton Campbell Crockett:
Squid received an HTTP/1.1 request from the client. Squid changed
the protocol to HTTP/1.0 for the next hop. Squid received an HTTP/
1.1 response, shouldn't Squid pass the
lör 2006-06-24 klockan 16:25 -0700 skrev Merton Campbell Crockett:
> Squid received an HTTP/1.1 request from the client. Squid changed
> the protocol to HTTP/1.0 for the next hop. Squid received an HTTP/
> 1.1 response, shouldn't Squid pass the HTTP header fields that it
> doesn't understa
On 24 Jun 2006, at 16:01 , Henrik Nordstrom wrote:
lör 2006-06-24 klockan 15:47 -0700 skrev Merton Campbell Crockett:
My understanding is that a server receiving an HTTP/1.0 request is
supposed to respond using the same version of the protocol.
No, a server should respond with the highest p
lör 2006-06-24 klockan 15:47 -0700 skrev Merton Campbell Crockett:
> My understanding is that a server receiving an HTTP/1.0 request is
> supposed to respond using the same version of the protocol.
No, a server should respond with the highest protocol version it
supports. But there is some feat
Currently, I am using Squid-2.5STABLE6 to implement a load-balanced,
redundant proxy array. I am investigating problems involving the
following and where a portion of the content on a web server requires
authentication.
Internet Explorer 6.x on a Windows XP system
Squid-2.5
