Tag Info

New answers tagged

0

The Palo Alto firewall can be set to use a Decryption policy to inspect the traffic after it passes through the Squid proxy. This will then allow the Palo Alto to see the decrypted traffic and once again assign meaningful App-IDs. See How to Implement SSL Decryption.


2

nginx can be considered a "reverse" proxy (due to its "upstream servers" functionality).... when in this role, it is effectively a "load balancer". a "normal" proxy, such as squid http proxy, socks, etc... fetches content on end user behalf, and sits in front of end users, making tcp/ip calls out to the internet web servers and ideally caching content. ...


0

Working solution eventually! Edit /etc/hosts and add: 127.0.0.1 tunnelproxy1 127.0.0.1 tunnelproxy2 127.0.0.1 tunnelproxy3 127.0.0.1 tunnelproxy4 Then go to /etc/squid3/squid.conf and: http_access allow all http_port 3128 cache_peer tunnelproxy1 parent 9001 0 round-robin no-query no-digest cache_peer tunnelproxy2 parent 9002 0 ...


1

Nginx is a web server... so it is not being used to replace squid very frequently ;) (Nginx proxy mode is different, it is used basically to transfer http requests to another server)


0

Don't use Rewrite for this, use a simple proxy. It seems you need something described here.


1

I figured out how to fix my issue. Whilst drookie's suggestion to create and ACL for the reverse proxy and apply the tcp_outgoing_address tag to it almost seemed obvious, I had no clue where to begin, let alone how the ACLs are defined / processed. First I had to figure out how the Squid.conf is interpreted (ie. top-to-bottom for first-matched ACLs) and ...


1

Create an ACL for the reverse-proxy traffic and set tcp_outgoing_address <<LAN-IP-HERE>> for it.


0

Not easily. By default, HTTPS connections are encrypted and you can't pass them through a proxy... what you could do is filter them by the destination IP, by allowing only some addresses and denying everything else using the firewall; however some servers use virtual hosts and host different websites under the same IP, so if the same server hosts both a ...


0

Using aptitude is even easier: sudo aptitude purge ~nsquid It will remove every package that contains squid in its name.


0

We have a lot of ways to purge. Example 2 ways I alway use: With client using MacOS or Linux: curl -X PURGE http://URL.of.Site/ABC.txt Direct on server which is running Squid: squidclient -m PURGE http://URL.of.Site/ABC.txt Absolutely, squid.conf must add acl Purge method PURGE http_access allow localhost Purge http_access allow localnet Purge ...


0

I got the same behaviour with Squid 3.3.8 (package up to date on Ubuntu 14.10 at the time of writing) After digging here, I found out that the cache mishandling of CSS and JS when the Vary Header is present was effectively a bug, fixed in posterious releases. Installing Squid 3.4.10 from the sources, makes disapear this issue.



Top 50 recent answers are included