Search squid archive

Re: "invalid header" error by https access

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: Dominik Schmid <dominik_schmid@xxxxxx>
Subject: Re: "invalid header" error by https access
From: Henrik Nordstrom <hno@xxxxxxxxxxxxxxx>
Date: Sat, 1 Oct 2005 03:10:23 +0200 (CEST)
Cc: Squid Users <squid-users@xxxxxxxxxxxxxxx>
Delivered-to: mailing list squid-users@xxxxxxxxxxxxxxx
In-reply-to: <433DCF6B.1060209@xxxxxx>
Mailing-list: contact squid-users-help@xxxxxxxxxxxxxxx; run by ezmlm
References: <433C2CE4.4020302@xxxxxx> <Pine.LNX.4.61.0509302138430.13819@xxxxxxxxxxxxxxxxxxxxx> <433DCF6B.1060209@xxxxxx>

On Sat, 1 Oct 2005, Dominik Schmid wrote:

Then tell me why it works on squid 2.4?


Because Squid-2.4 did not support persistent connections on error pages.

There must be something changed in squid 2.5 ........

Yes, error pages now support persistent connections to support NTLMauthentication.


Regards
Henrik

References:
- "invalid header" error by https access
  - From: Dominik Schmid
- Re: "invalid header" error by https access
  - From: Henrik Nordstrom

Prev by Date: RE: transparent configuration with upstream proxy
Next by Date: Re: transparent configuration with upstream proxy
Previous by thread: Re: "invalid header" error by https access
Next by thread: Re: "invalid header" error by https access
Index(es):
- Date
- Thread

[Index of Archives] [Linux Audio Users] [Samba] [Big List of Linux Books] [Linux USB] [Yosemite News]

Powered by Linux