ok again i filter out most of the squid conf with this minimum config should
i get any static img or anything as hit or not
caus i dont get any
i test on squid 3.5.8 and up same think
via off
forwarded_for off
# should be allowed
acl localnet src 10.2.3.0/24
acl localnet src 10.2.2.0/24
acl l
hi this is the first time that happen to me i don't know if its bug or old
stupidity from my side
ok the problem i did not do more study yet i need more feed back pls
let say i have
acl redirect urlpath_regex -i &ir\=1&rr\=12
no_cache deny redirect
all is fine until now caching is ok hit is o
"Linda A. Walsh" schreef:
Enough to verify what I am saying, usually, but I have expert
knowledge in almost no field that I know of.
Doesn't matter. All that matters is where you want to go and what you
need for that.
I have this feeling that I like SPDY better than HTTP2? Anyone agree?
On 8/10/2015 1:28 a.m., Job wrote:
> Hi Amos!
>
> Resolved: in squid.conf i have to write ip:port instead of :port.
> As example, 192.168.10.254:3129 works with interception.
>
> Only with :3129 it does not works!
Try it without the colon. You only need a colon to separate the
ip/hostname and po
Xen wrote:
Thanks for mentioning it here, I didn't even know about it, like you.
And of course you study it really well before commenting.
---
Enough to verify what I am saying, usually, but I have expert
knowledge in almost no field that I know of. I do have
fundamentals that help me build u
Linda, Linda Walsh everywhere :p.
I only trashed your message. I love to trash Linda Walsh :P :P.
Okay, pointless message.
On Sun, 11 Oct 2015, Linda A. Walsh wrote:
The protocol usage in the 2nd case used 'http2' -- which started me
wondering what the heck that was...so googled around and
The Squid HTTP Proxy team is very pleased to announce the availability
of the Squid-3.5.10 release!
This release is a bug fix release resolving issues found in the prior
Squid releases.
The major changes to be aware of:
* Regression Bug 4326: base64 binary encoder rejects data beginning
wit
__
Squid Proxy Cache Security Update Advisory SQUID-2015:3
__
Advisory ID:SQUID-2015:3
Date: September 17, 2015
Summary:
The Squid HTTP Proxy team is very pleased to announce the availability
of the Squid-3.5.9 release!
This release is a security and bug fix release resolving issues found in
the prior Squid releases.
The major changes to be aware of:
* SQUID-2015:3 Multiple Remote Denial of service issues in SS
On 12/10/2015 11:31 a.m., Linda A. Walsh wrote:
>
> I was looking at some traffic differences between one of
> my browsers going through squid and going direct (via masquerade).
>
> The protocol usage in the 2nd case used 'http2' -- which started me
> wondering what the heck that was...so googled
Em 11/10/15 19:31, Linda A. Walsh escreveu:
Are the impacts or implementation details
being thought about in squid?, since if it comes
down to it only being supported by encrypted
TUNNELS, its not only going to be hard to cache,
but also makes it a pain to implement http/browsing
controls on con
On 10/10/2015 12:48 p.m., SaRaVanAn wrote:
> Hi All,
> I have compiled squid version 3.5.10 in debian wheezy 7.1. With the
> updated version squid+tproxy4 is not working in debian. I am getting the
> below error if I try to browse any webpage. Also the connection gets reset.
>
Wheezy kernel and
12 matches
Mail list logo
