g, 16. Mai 2006 17:34
To: Baumgaertel, Oliver
Cc: Adrian Chadd; squid-dev@squid-cache.org
Subject: Re: NTLM forwarding in 2.6 ?
I'm still not what sure what you mean; do you mean clients will speak
NTLM to
the intranet server but have squid configured as a web proxy?
Adrian
On Tue, Ma
coming Stable 2.6/3 as
we've to start planning for the nescessary changes rather soon.
-Original Message-
From: Adrian Chadd [mailto:[EMAIL PROTECTED]
Sent: Dienstag, 16. Mai 2006 09:44
To: Baumgaertel, Oliver
Cc: squid-dev@squid-cache.org
Subject: Re: NTLM forwarding in 2.6 ?
Are you r
Hi.
Are there any plans to add NTLM forwarding to the Stable 2.6 release?
I ask because we will need that in the coming months and I'd like to
safe the 30 or so squid boxes currently running in the third layer. Else
they'd surely follow the other 20 already replaced by BlueCoats.
regards,
Olive
>> I've sniffed a bit of the traffic and saw that Squid actually tries to
>> "cwd" through the whole path, one layer at a time, while all others
>> directly "cwd" into the target directory with one request.
> See RFC1738 "3.2.2. FTP url-path" for why...
>If you want to CWD directly into the di
Hi all.
It's not just Stable12, I've also tested that with Stable6 and Stable4
...
In the case a user requests a directory listing and he does have the
proper rights for the target directory, but not for the path leading to
it, Squid responds with a 404 (ftp 550). When using any other proxy
(Blue
Hello all.
We have 2 Farms, an inner(intranet, just as a filter, no hdd caching)
and an outer(DMZ, just hdd chaching) one. We use CARP to optimise the
caching in the outer proxies. Now, all connect requests are routed to
only one single machine. While that wasn't an issue in the last years,
we hav
Typically you'd use the "Expires" header with a negative time value,
meaning a date string that's at least 1 second in the past.
But "Cache-Control:" or "Pragma:" with a max-age=0, no-store or a
no-cache directive should prevent any storing in a cache either, else
it's not conform to the RFC. Bu
Well, actually that's not the case.
When I proposed to my superiours to let me help get S3 stable I got the
very clear command to concentrate on S2.5. As the feature freeze of S2.5
didn't permit to do any useful work for us (ICAP) I didn't get
permission to do anything at all beside porting all
Hi all.
We encountered several segvfaults a day with active challenge reuse.
However, since we also use the icap patch which prevents keep-alive together
with ntlm, disabling the reuse was not an option.
Because of some changes we also had to activate ntlm negotiate. Since then
all our 10 squids
>>> Baumgaertel Oliver wrote:
>>> I do understand that there were a couple of people in the past asking
>>> for exactly that and it was denied. I am currently in the position to
>>> have the freedom to start a new icap code project. But before I dive
>>&g
Hi all.
My company uses squid with ntlm and icap. That's a very unlucky combination
I understand, as the history tells us that it's an unstable one.
I've managed to fix or work around the various assertions in 2.5.STABLE6, so
that we can be sure it's not crashing. You see, our farms are the front
Hallo all.
I'd like the icap-2_5.patch I got from devel.squid-cache.org to run with
squid-2.5.STABLE9.
To have a chance to make it fit I'd need at least to know which code base it
was made for in the first place. Someone able to point me in the right
direction?
Regards, Oliver Baumgaertel.
Hello all.
I've recently started working for Siemens Erlangen/Germany and I am part of
the administration team managing our Squid proxy farms. As the teams sole
C/C++ programmer it'll be my responsibility to address code related issues.
That'll be mostly modifying/adding internal patches/feat
13 matches
Mail list logo