Turns our I just needed the
never_direct allow all
in the right spot of course.
Cheers,
Ben
> well the answer is you other mail + the squid.conf
>
> "Without the cache_peer I can not get to any sties at all. All
> internet (well, http and https) traffic on our network must go through
> the paren
On 7/12/2012 1:21 AM, Crawford, Ben wrote:
As requested, a more detailed squid.conf:
acl manager proto cache_object
acl localhost src 127.0.0.1/32 ::1
acl localnet src 10.161.128.0/20
acl to_localhost dst 127.0.0.0/8 0.0.0.0/32 ::1
acl SSL_ports port 443
acl Safe_ports port 80 # http
acl
Sorry for double reply, sent that last one out a bit quicker than I should have.
On 12 July 2012 04:25, Eliezer Croitoru wrote:
> two things:
> post a more detailed squid.conf to see if there is something wrong there.
>
> i am using squid3.1.19 and 3.2.16-17 and it works like for many others.
> t
As requested, a more detailed squid.conf:
acl manager proto cache_object
acl localhost src 127.0.0.1/32 ::1
acl localnet src 10.161.128.0/20
acl to_localhost dst 127.0.0.0/8 0.0.0.0/32 ::1
acl SSL_ports port 443
acl Safe_ports port 80 # http
acl Safe_ports port 21 # ftp
acl Safe_p
two things:
post a more detailed squid.conf to see if there is something wrong there.
i am using squid3.1.19 and 3.2.16-17 and it works like for many others.
this problem can be an issue about routing and not related to squid at all.
a 504 code is:
10.5.5 504 Gateway Timeout
The server, while a
Hi All,
I have run into a problem with not being able to access a few specific
things on the web when running through our local proxy.
Some details:
* The current setup is a Linux box running squid 3.1.19.
* This is being run behind a pfsense box that is load balancing our
two internet connection