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

2016-10-21 Thread Yuri Voinov
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 But I think it will be quite sufficient to bring back one of the options HTTP violations, namely - "Ignore cache-control". That's all. The rest we do ourselves. 22.10.2016 1:28, Yuri Voinov пишет: > > This is inappropriate. Just all we are need t

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

2016-10-21 Thread Yuri Voinov
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 This is inappropriate. Just all we are need that to make the option "F*ck the RFC and f*ck anyone who opposes caching" in the SQUID. 22.10.2016 1:07, Eliezer Croitoru пишет: > Instead of modifying the code, would you consider to use an ICAP servi

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

2016-10-21 Thread Eliezer Croitoru
Instead of modifying the code, would you consider to use an ICAP service that will mangle this? I am unsure about the risks about doing so but why patch the sources if you can resolve it with the current mainstream capabilities and API? Eliezer Eliezer Croitoru

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

2016-10-21 Thread James Lay
On 2016-10-21 09:58, Leandro Barragan wrote: James, thanks for your advice! I've read your email on this list about LibreSSL. I tried to compile Squid with LibreSSL in the first place because of what you wrote about ChaCha20. But unfortunately, I couldn't, compilation stopped because of some obsc

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

2016-10-21 Thread Leandro Barragan
James, thanks for your advice! I've read your email on this list about LibreSSL. I tried to compile Squid with LibreSSL in the first place because of what you wrote about ChaCha20. But unfortunately, I couldn't, compilation stopped because of some obscure error. Do you remember what version of squ

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

2016-10-21 Thread Heiler Bemerguy
Hello, I've limited the "vary" usage and gained some hits by making these modifications (in blue) to the http.cc code: while (strListGetItem(&vary, ',', &item, &ilen, &pos)) { SBuf name(item, ilen); if (name == asterisk) { */** vstr.clear(); break; **/ * *

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

2016-10-21 Thread James Lay
On 2016-10-20 20:15, Leandro Barragan wrote: Thanks for your time Alex! I modified my original config based on Amos recommendations, so I think now I have a more consistent peek & splice config: acl TF ssl::server_name_regex -i facebook fbcdn twitter reddit ssl_bump peek all ssl_bump terminat

[squid-users] sourcehash load balance

2016-10-21 Thread André Janna
I set up a Squid proxy that forwards all requests to 2 parent caches. I'm using Squid version 3.5.19. My goal is that multiple connection from a client to a server should be forwarded to the same parent, so that the server see all requests coming from the same IP address. I'm using the followi

Re: [squid-users] FTP : Squid sending private IP in PASV response

2016-10-21 Thread Garri Djavadyan
On Fri, 2016-10-21 at 08:27 +, Gael Ancelin wrote: > WAN_IP---[FW]---localIP1-[SQUID]-localIP2localIP3- > [FTP_Server] > > I was expecting something like "227 Entering Passive Mode > (54,xx,xx,xx,213,249)."  > with public ip. > What I want is a response like (WAN_IP,port), but

Re: [squid-users] FTP : Squid sending private IP in PASV response

2016-10-21 Thread Gael Ancelin
Hello, Thanks for your interest. As resquested, here is my FTP related configuration : acl FTP proto FTP http_access allow FTP always_direct allow FTP ftp_port 21 accel defaultsite= protocol=FTP --- On Squid itself -- ftp> open 127.0.0.1 Connected to 127.0.0.1 (127.0.0.1). 220 Servic