Your test is broken.
" curl http://www.ciudad.com.ar -x http://SQUIDIP:80 "
tells curl to fetch from a *forward-proxy* listening at SQUIDIP:80.
The HTTP syntax for port 80 (web server / reverse-proxy) and for port
3128 (forward-proxy) is significantly different in ways which open
security vulne
Same configuration with Squid-3.2.13 and the same problem:
connect(11, {sa_family=AF_INET, sin_port=htons(80),
sin_addr=inet_addr("SQUIDIP")}, 16) = -1 EINPROGRESS (Operation now in
progress)
Something related to configure line?
On Wed, Jul 23, 2014 at 5:54 PM, Roberto O. Fernández Crisial
wrot
Nicolas,
I do not use client and server on the same machine.
The Squid 3.1.10 has been installed via "yum". The Squid 3.4.6 has
been compiled using: "./configure --prefix=/usr/local/squid-3.4.6
-enable-icap-client --enable-ssl --enable-ssl-crtd
--with-default-user=squid --enable-ltdl-convenience
Hi Roberto,
El 23/07/2014 20:54, Roberto O. Fernández Crisial escribió:
Hi guys,
I hope you're doing fine. I'm trying to intercept HTTP requests on
Squid 3.4.6 but I'm going crazy. Is there any http_port parameter
change between 3.1.10 and 3.4.6?
I have 3.1.10 working fine, here are the exampl
Hi guys,
I hope you're doing fine. I'm trying to intercept HTTP requests on
Squid 3.4.6 but I'm going crazy. Is there any http_port parameter
change between 3.1.10 and 3.4.6?
I have 3.1.10 working fine, here are the examples:
IPTABLES CONFIGURATION (Global config)
-A PREROUTING -s 10.1.0.0/16 -p
