OK it's pretty simple to reproduce on any machine what so ever on 3.5.15-2.
open two terminals on two machines more or less.
Then run on one the next command
watch -n 0.2 "http_proxy=http://IP_OP_PROXY:3128/ curl --silent --range
20-40 http://ngtech.co.il/squid/videos/sosp2011_27.mp4 | wc -c"
Hey,
Thanks for the debug!.
I do not know the exact reason but I can say for sure that it's not the
NetAPP or any other OS level issue since the AUFS\UFS cache_dir works
fine in the same system and in a similar situation.
I will try to replicate it locally.
I do understand the issue and I
On Sun, 2016-03-13 at 00:09 +1100, Tim Bates wrote:
> Is it possible to do this:
>
> * Intercept HTTPS and send it via Squid?
> * Apply ACLs to the intercepted HTTPS traffic based on host/domain name?
> * Not change any configuration on clients?
>
> Should I keep researching how this peeking
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
http://wiki.squid-cache.org/ConfigExamples/Intercept
http://wiki.squid-cache.org/ConfigExamples/Intercept/SslBumpExplicit
http://wiki.squid-cache.org/SquidFaq/SquidAcl
12.03.16 19:09, Tim Bates пишет:
> Is it possible to do this:
>
> * Intercept
Is it possible to do this:
* Intercept HTTPS and send it via Squid?
* Apply ACLs to the intercepted HTTPS traffic based on host/domain name?
* Not change any configuration on clients?
Should I keep researching how this peeking and bumping and splicing and
such works, or is it impossible?
TB
