Re: [squid-users] Caching http google deb files

Well you are right about that but for me it’s simpler to Write and ICAP service to do that then hack squid code. Eliezer Eliezer Croitoru Linux System Administrator Mobile: +972-5-28704261 Email: elie...@ngtech.co.il From: Heiler Bemerguy

Re: [squid-users] Caching http google deb files

Hi Eliezer I've never used ICAP, and I think hacking the code is way faster than creating/using a separate service for that. And I'm not sure, but I don't think I can manage to get this done with current squid's options. This patch will make squid NOT ignore the objects with "*Vary: **"

Re: [squid-users] possible to intercept https traffic in TCP_TUNNEL CONNECT method ?

On Saturday 22 October 2016 at 15:42:23, --Ahmad-- wrote: > Hi guys > say that i have squid proxy sever > and i was running capturing traffic on that server . You mean using ICAP or ECAP service? > say that all users were using ip:port —> ((tcp_connect tunnel))) mode of > squid I'm not sure

Re: [squid-users] Peeking on TLS traffic: unknown cipher returned

Excellent...glad it worked. James On Sat, 2016-10-22 at 10:35 -0300, Leandro Barragan wrote: > Thanks a lot James, compiling Squid 3.5.22 using that specific commit > of LibreSSL worked as a charm! I no longer have that "unknown cipher > returned" errors. I do have some errors with a tiny amount

Re: [squid-users] Caching Google Chrome googlechromestandaloneenterprise64.msi

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 22.10.2016 19:32, gar...@comnet.uz пишет: > On 2016-10-22 17:56, Antony Stone wrote: >> Disclaimer: I am not a Squid developer. >> >> On Saturday 22 October 2016 at 14:43:55, gar...@comnet.uz wrote: >> >>> IMO: >>> >>> The only reason I believe

[squid-users] possible to intercept https traffic in TCP_TUNNEL CONNECT method ?

Hi guys say that i have squid proxy sever and i was running capturing traffic on that server . say that all users were using ip:port —> ((tcp_connect tunnel))) mode of squid the question is being asked here … will i be able to see https traffic like Facebook as normal traffic ? or

Re: [squid-users] Peeking on TLS traffic: unknown cipher returned

Thanks a lot James, compiling Squid 3.5.22 using that specific commit of LibreSSL worked as a charm! I no longer have that "unknown cipher returned" errors. I do have some errors with a tiny amount of sites, but I suppose its because of server-side misconfigurations that LibreSSL simply don't

Re: [squid-users] Caching Google Chrome googlechromestandaloneenterprise64.msi

On 2016-10-22 17:56, Antony Stone wrote: Disclaimer: I am not a Squid developer. On Saturday 22 October 2016 at 14:43:55, gar...@comnet.uz wrote: IMO: The only reason I believe [explains] why core developers of Squid tend to move HTTP violating settings from average users is to prevent

Re: [squid-users] Caching Google Chrome googlechromestandaloneenterprise64.msi

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 I will explain why I am extremely outraged by this position. Every single major players - both from the Web companies and from suppliers caching solutions (BlueCoat, ThunderCache etc.) - to one degree or another violate RFC. And developers of

Re: [squid-users] Caching Google Chrome googlechromestandaloneenterprise64.msi

Disclaimer: I am not a Squid developer. On Saturday 22 October 2016 at 14:43:55, gar...@comnet.uz wrote: > IMO: > > The only reason I believe [explains] why core developers of Squid tend to > move HTTP violating settings from average users is to prevent possible > abuse/misuse. I believe the

Re: [squid-users] Caching Google Chrome googlechromestandaloneenterprise64.msi

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 22.10.2016 18:43, gar...@comnet.uz пишет: > On 2016-10-22 16:05, Yuri Voinov wrote: >> Good explanations do not always help to get a good solution. A person >> needs no explanation and solution. >> >> So far I've seen a lot of excellent reasons

Re: [squid-users] Caching Google Chrome googlechromestandaloneenterprise64.msi

On 2016-10-22 16:05, Yuri Voinov wrote: Good explanations do not always help to get a good solution. A person needs no explanation and solution. So far I've seen a lot of excellent reasons why Squid can not do so-and-so in the normal configuration. However, this explanation does not help in

Re: [squid-users] Caching Google Chrome googlechromestandaloneenterprise64.msi

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 22.10.2016 16:55, gar...@comnet.uz пишет: > On 2016-10-22 13:53, Rui Lopes wrote: >> Hello, >> >> I'm trying to receive a cached version of >> googlechromestandaloneenterprise64.msi with: >> >> refresh_pattern

Re: [squid-users] Caching Google Chrome googlechromestandaloneenterprise64.msi

On 2016-10-22 13:53, Rui Lopes wrote: Hello, I'm trying to receive a cached version of googlechromestandaloneenterprise64.msi with: refresh_pattern googlechromestandaloneenterprise64\.msi 4320 100% 4320 override-expire override-lastmod reload-into-ims ignore-reload ignore-no-store

Re: [squid-users] Caching Google Chrome googlechromestandaloneenterprise64.msi

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Try to use store-ID. Your URL seems dynamic. So, Squid never can cache it. Don't forget - Google, like many other web companies, actively counteracts caching. It is likely that you even Store ID will not help. 22.10.2016 14:53, Rui Lopes пишет:

[squid-users] Caching Google Chrome googlechromestandaloneenterprise64.msi

Hello, I'm trying to receive a cached version of googlechromestandaloneenterprise64.msi with: refresh_pattern googlechromestandaloneenterprise64\.msi 4320 100% 4320 override-expire override-lastmod reload-into-ims ignore-reload ignore-no-store ignore-private and trying it with the following