On 26/10/2015 4:28 a.m., rudi wrote:
> Hey Amos,
>
> thank you very much for your very helpful information. Now i have an access
> control an SSL is fixed too but i had to add port 80 as SSL port to use the
> proxies as https proxy in proxifier.
>
> One more question. Now i can use the proxies fr
On 26/10/2015 6:28 a.m., David Touzeau wrote:
>
> I think you are right Amos, but could you explain why in 3.2x, 3.4x
> branchs (exactly 3.4.6 ) there is no issue.
> And samba was the same version...
I'm not sure why 3.4 would work and not 4.x. The code has not changed
since 3.4.2, and not in a w
On 26/10/2015 5:23 a.m., Chico Venancio wrote:
> Is everyone still having this issue?
> We tried messing arround with the .conf and used a 32bit debian as well to
> no avail.
>
No. Just those of you having it.
I am suspecting that the problem is related to CONNECT tunnels. Since
HTTPS traffic is
On 26/10/2015 12:48 p.m., Alex Samad wrote:
> HI
>
> I have had a look at http://wiki.squid-cache.org/Features/DelayPools
>
> Wondering if somebody can maybe explain how it rate limits downloads.
>
Quite simple. Each request transaction gets assigned into some pool(s)
based on your delay_parame
On 26/10/2015 9:53 a.m., Yuri Voinov wrote:
>
> I can not understand why so much dropped for caching of https.
I dont understand what you mean by that.
You started caching HTTPS and ratio dropped?
HTTPS is less than 30% of total traffic. But;
* has a higher proportion of Cache-Control: privat
On 26/10/2015 8:29 a.m., Yuri Voinov wrote:
>
> In a nutshell - I need no possible explanation. I want to know - it's a
> bug or so conceived?
Well, I don't think it is what you think.
For starters ignore-no-cache was removed back in 3.2, so your 3.4
version working okay shows that its not that
I cannot speak for the Squid project and you may ask the squid-dev more
about it and also see the release notes about it.
What I can is that the phrase "it's not a bug, it's a feature" can work
the other way around "it's not a feature, it's a bug" and as you have
mentioned "it worked yesterday"
HI
I have had a look at http://wiki.squid-cache.org/Features/DelayPools
Wondering if somebody can maybe explain how it rate limits downloads.
So I can understand it would be able to limit proxy to client traffic
as squid is the sender and can limit how it sends.
But if I want to limit speed fro
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
I can not understand why so much dropped for caching of https. This is
very critical in the modern conditions, for obvious reasons. In older
versions of the same for this to work. And it does not have the
slightest desire to write or use a third-pa
On 25/10/2015 21:28, Yuri Voinov wrote:
It's not about that. It's about the fact that, with exactly the same
parameters caching and maintaining the cache at the same URL, which I
used to get 85% cache hit, I am now, with a SQUID 4, I get 0%. That's all.
OK then, if it's that important for you a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
In a nutshell - I need no possible explanation. I want to know - it's a
bug or so conceived?
26.10.15 1:17, Eliezer Croitoru пишет:
> Hey Yuri,
>
> I am not sure if you think that Squid version 4 with extreme low hit
ratio is bad or not but I can
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Actually, I'm experienced enough not to need retelling truths. I'm aware
of, and how difficult it is to cache dynamic content, and it's exactly
what I wrote Vicki why it is impossible to cache YouTube :).
It's not about that. It's about the fact t
Hey Yuri,
I am not sure if you think that Squid version 4 with extreme low hit
ratio is bad or not but I can understand your sight about things.
Usually I am redirecting to this page:
http://wiki.squid-cache.org/Features/StoreID/CollisionRisks#Several_real_world_examples
But this time I can p
Le 25/10/2015 09:01, Amos Jeffries a écrit :
On 25/10/2015 5:47 a.m., David Touzeau wrote:
auth_param ntlm program /usr/bin/ntlm_auth --domain=TOUZEAU.BIZ
--helper-protocol=squid-2.5-ntlmssp
auth_param ntlm children 20 startup=5 idle=3
auth_param ntlm keep_alive on
authenticate_ttl 14400 seco
Is everyone still having this issue?
We tried messing arround with the .conf and used a 32bit debian as well to
no avail.
Chico Venancio
> 2015-10-14 0:03 GMT-03:00 Amos Jeffries :
>>
>> On 14/10/2015 11:46 a.m., Chico Venancio wrote:
>> > I have configured delay pools for a client that delays ac
Hey Amos,
thank you very much for your very helpful information. Now i have an access
control an SSL is fixed too but i had to add port 80 as SSL port to use the
proxies as https proxy in proxifier.
One more question. Now i can use the proxies from
193.xxx.xxx.x1/255.255.255.xxx. But if i want to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi gents,
Pay attention to whether someone from the test SQUID 4 as extremely low
of cache hits from the new version? Particularly with respect to sites
HTTPS directive "no cache"? After replacing the Squid 3.4 to 4 squid
cache hit collapsed from
On 25/10/2015 3:49 a.m., rudi wrote:
> Hey guys,
>
> im trying to setup squid for windows. I have different IPs on my server and
> i want to assign them to VMs:
> VM1 --> Outgoing IP1
> VM2 --> Outgoing IP2
> ...
>
> So far this is working! But now i want to deny all other IPs to avoid false
> a
On 25/10/2015 9:01 p.m., Amos Jeffries wrote:
> On 25/10/2015 5:47 a.m., David Touzeau wrote:
>>
>> auth_param ntlm program /usr/bin/ntlm_auth --domain=TOUZEAU.BIZ
>> --helper-protocol=squid-2.5-ntlmssp
>> auth_param ntlm children 20 startup=5 idle=3
>> auth_param ntlm keep_alive on
>> authenticat
On 25/10/2015 5:47 a.m., David Touzeau wrote:
>
> auth_param ntlm program /usr/bin/ntlm_auth --domain=TOUZEAU.BIZ
> --helper-protocol=squid-2.5-ntlmssp
> auth_param ntlm children 20 startup=5 idle=3
> auth_param ntlm keep_alive on
> authenticate_ttl 14400 seconds
> authenticate_cache_garbage_inte
20 matches
Mail list logo
