I filed that bug and it seems to have been getting a fair bit of attention from
other squid users who are suffering from it, but still no traction from anyone
that's able to diagnose it for some reason.
I’m not on the dev mailing list because I’m not a developer, but I would
welcome anyone
On 13/04/2014 7:10 p.m., Dan Charlesworth wrote:
I filed that bug and it seems to have been getting a fair bit of attention
from other squid users who are suffering from it, but still no traction from
anyone that's able to diagnose it for some reason.
I’m not on the dev mailing list
On 13/04/2014 7:08 a.m., Nick Hill wrote:
I have been ironing out issues with my windows updates set-up for
Squid. I have been through my squid.conf file to de-cruft it.
The following squid.conf should be self-documenting. I have found this
works well in a multi-computer environment where
On 12/04/2014 5:23 p.m., Amm wrote:
Hello,
I accidentally came across this. I was trying to test what TLS version
my squid reports.
So I ran this command:
openssl s_client -connect 192.168.1.2:8081
where 8081 is https_port on which squid runs. (with sslbump)
And BOOM, squid went in
On 04/13/2014 04:27 PM, Amos Jeffries wrote:
On 12/04/2014 5:23 p.m., Amm wrote:
So I ran this command:
openssl s_client -connect 192.168.1.2:8081
where 8081 is https_port on which squid runs. (with sslbump)
And BOOM, squid went in to infinite loop! And started running out of
file
Dear Amos
Thank you for reviewing the config and giving your deeply considered comments.
On 13 April 2014 09:56, Amos Jeffries squ...@treenet.co.nz wrote:
Did your tests find any actual benefits in these override-lastmod
override-expire ignore-reload ignore-must-revalidate ignore-private
Why https_port? and why ssl_bump on https_port ?
it should run ontop of http_port as far as I can understand and know.
There was an issue which I reported about and which is similar and I
have used couple acls to block the access and the loop from the port to
itself.
Eliezer
On 04/13/2014
On 04/13/2014 08:35 PM, Eliezer Croitoru wrote:
Why https_port? and why ssl_bump on https_port ?
it should run ontop of http_port as far as I can understand and know.
https_port is needed when you intercept port 443 traffic.
http_port intercepts port 80 and https_port intercepts port 443.
On 13 April 2014 16:11, Nick Hill n...@nickhill.co.uk wrote:
To paraphrase the logic coded here:
Don't cache anything with a query string UNLESS it matches the ACL
wupdatecachablequery.
another way to write this more succinctly might be:
cache deny QUERY
cache allow wupdatecachablequery
There is now a patch in the bug report which seems to fix this issue and
a few others. http://bugs.squid-cache.org/show_bug.cgi?id=3982
I would like confirmation (in the bug report please) from some others
testing before this gets applied.
Cheers
Amos
10 matches
Mail list logo
