That's not how HTTP works. What are you using to collect these
statistics?
On 14/07/2008, at 10:59 PM, Russell Suter wrote:
Amos Jeffries wrote:
Russell Suter wrote:
Hi,
I have a question with regards to persistent connections to a
cache peer
parent. I have
multiple users connecting
On mån, 2008-07-14 at 06:59 -0600, Russell Suter wrote:
> To me, the behavior is broken.
No.
> Either the single connection
> to the cache parent should provide the correct user
> credentials, or there should be one persistent connection per
> user.
Authentication in HTTP is per message, not per
On lör, 2008-07-12 at 16:24 -0600, Russell Suter wrote:
> What seems to happen is that a persistent connection is made to the
> appliance. This in
> and of itself isn't a problem except that all of the different users
> show up as the first user
> that made the initial connection. This really
Amos Jeffries wrote:
Russell Suter wrote:
Hi,
I have a question with regards to persistent connections to a cache peer
parent. I have
multiple users connecting through a custom compiled Squid.2.6.STABLE17
(also tried
3.0.STABLE7) on a RedHat EL 4 box in front of a commercial web filter
a
Russell Suter wrote:
Hi,
I have a question with regards to persistent connections to a cache peer
parent. I have
multiple users connecting through a custom compiled Squid.2.6.STABLE17
(also tried
3.0.STABLE7) on a RedHat EL 4 box in front of a commercial web filter
appliance. In my
squid.
Hi,
I have a question with regards to persistent connections to a cache peer
parent. I have
multiple users connecting through a custom compiled Squid.2.6.STABLE17
(also tried
3.0.STABLE7) on a RedHat EL 4 box in front of a commercial web filter
appliance. In my
squid.conf file, I have the
