Hi Olivier,
I think on some of your newer clients you have an issue with Negotiate and
NTLM fallback. If I look at
https://msdn.microsoft.com/en-us/library/ff468736.aspx I see this
https://i-msdn.sec.s-msft.com/dynimg/IC426444.gif
If I interpret this correctly the client will try NegoEx
Hi Amos,
>> I failed to mention that I am on 3.5.1. And, readSomeData() is already
>> "fixed":
>
> Bug 4353 exists because the initial fix for 4206 was not enough to fully
> remove the behaviour. Sometimes yes, sometimes no.
>
> Only the nasty hack of allocating buffers twice and throwing one awa
On 6/11/2015 5:21 a.m., Fabio Almeida wrote:
> Hi folks,
>
> I have and Squid 3.5.10 instance that I can't reconfigure, it crashes if
> there's many spawned ldap helpers.
> But, if there's not many people connect it reconfigure normal as expected.
>
> It's running on a FreeBSD 10.1-RELEASE-p19 am
On 6/11/2015 4:47 a.m., John Smith wrote:
> Amos,
>
> Thanks (again) very much for the reply.
> The news does not surprise me at all, but I needed to ask the questions.
>
> Let's assume I could require a different port for http and https, and
> cleaned up the squid configurations like we did priv
Hi folks,
I have and Squid 3.5.10 instance that I can't reconfigure, it crashes if
there's many spawned ldap helpers.
But, if there's not many people connect it reconfigure normal as expected.
It's running on a FreeBSD 10.1-RELEASE-p19 amd64 with the following
./configure line:
./configure --wit
Amos,
Thanks (again) very much for the reply.
The news does not surprise me at all, but I needed to ask the questions.
Let's assume I could require a different port for http and https, and
cleaned up the squid configurations like we did privately for http. How
hard would it be to solve either ca
On 5/11/2015 7:16 a.m., John Smith wrote:
> Hi,
>
> I'm trying to improve our cache hit ratio. We have a fairly complicated
> layer of squid 3.10 proxies as previously detailed.
>
> Problem 1. Some of the traffic is identified by domain to go to another
> layer of proxies. I've called this pro
On 5/11/2015 10:41 p.m., Prashanth Prabhu wrote:
> Hello Amos,
>
> Thanks for the quick response.
>
> I failed to mention that I am on 3.5.1. And, readSomeData() is already
> "fixed":
Bug 4353 exists because the initial fix for 4206 was not enough to fully
remove the behaviour. Sometimes yes, s
On 5/11/2015 10:39 p.m., Edouard Gaulué wrote:
> Le 05/11/2015 04:18, Amos Jeffries a écrit :
>>
>> Depends on what Squid version you are using. It was broken for a few
>> years. We fixed that issue a few months back and it was apparently
>> working now. that Good news is you can grab the latest Sq
On 6/11/2015 12:30 a.m., maple wrote:
> Hi Amos,
>
> So, if I understand it right, it's impossible to do ssl-bump even I use the
> proxychains to chain the squid with my parent proxy without using
> cache_peer(because I'm confirmed that ssl-bump+cache_peer must not work in
> squid), am I right?
>
On 11/04/2015 08:55 PM, Edouard Gaulué wrote:
Hi Marcus,
Well that just an URL rewriter program. You can just test it from the command
line :
echo "URL" | /usr/bin/squidGuard -c /etc/squidguard/squidGuard.conf
Before I understood it was possible to precise the redirect code I got that:
#> ec
On 5/11/2015 10:54 p.m., joe wrote:
> HI Amos after diging and testing wat i found for you is
> TCP_REFRESH_MODIFIED/200 && TCP_SWAPFAIL_MISS/200 ar connected
>
> i will try to explain how dose that happen hoop that im clear enough for you
> to understand
>
>
> ok lets say the way you guy
Hi Amos,
So, if I understand it right, it's impossible to do ssl-bump even I use the
proxychains to chain the squid with my parent proxy without using
cache_peer(because I'm confirmed that ssl-bump+cache_peer must not work in
squid), am I right?
I just wonder how admin900710 make things work by u
HI Amos after diging and testing wat i found for you is
TCP_REFRESH_MODIFIED/200 && TCP_SWAPFAIL_MISS/200 ar connected
i will try to explain how dose that happen hoop that im clear enough for you
to understand
ok lets say the way you guys mod the code for the TCP_REFRESH_MODIFIED wen
the
Hello Amos,
Thanks for the quick response.
I failed to mention that I am on 3.5.1. And, readSomeData() is already "fixed":
void
ConnStateData::readSomeData()
{
if (reading())
return;
debugs(33, 4, HERE << clientConnection << ": reading request...");
if (!in.maybeMakeSpa
Le 05/11/2015 04:18, Amos Jeffries a écrit :
Depends on what Squid version you are using. It was broken for a few
years. We fixed that issue a few months back and it was apparently
working now. that Good news is you can grab the latest Squid code (v4 or
3.5), build it and use the helper generate
On 5/11/2015 7:44 p.m., maple wrote:
> hi Amos,
>
> what did you exactly refer to for "These particular use-case issue"?
SSL-bump for port 443 intercepted directly by the proxy doing the bumping.
https_port X intercept ssl-bump ...
If there is an upstream proxy relaying to this one (eg proxych
17 matches
Mail list logo
