Manual talk:Squid caching

If you have squid listening on port 80, your webserver will have to listen on a different port (if it's on the same machine).

How does squid know when a page has been changed and it needs to request a new one from Apache?

Thanks for this Tutorial. I got Squid working no as a reverse proxy.84.137.242.154 13:06, 20 July 2006 (UTC)

Warning: These Squid Cache configurations are outdated!
Squid cache has depreciated the use of several directives in version 2.6 which will make it impossible to set up with the settings given here. Please read the Squid Cache 2.6 release notes for more info.

The manual at the Squid Cache homepage is also out of date, so you may find it difficult to figure out these new settings. This manual explains many of the new directives, but be warned as this manual is intended for Squid Cache version 3.0 and some settings may not work as desired!

Hope this helps anyone who may be having trouble trying to install Squid Cache 2.6 with the httpd_accel_* directives. ech elon  08:29, 27 July 2006 (UTC)

Configuration should now work for 2.6
I have added two lines which replace all of the other http_accel settings in Squid 2.6. This tutorial should now be up to date with the latest stable Squid version. --166.70.232.84 17:23, 18 August 2006 (UTC)

Configuration modification
I've modified this configuration a little bit to make logging easier. Rather than have squid listen on port 80, I still have apache listen on port 80. For the , I have a ProxyPass / http://my.domain:3128/, which redirects the request to squid. Squid then sends the request back to apache, which has an alternate  which is the real site. This vhost has logging disabled, so entries won't show up twice, but every request, even the cached ones, do get logged. Staypuft 19:56, 6 December 2006 (UTC)

conflicting configuration...
I updated some of the 2.6 configuration to be a little more clear - before the Apache config conflicted with the "2.6" section since it was configuring squid to bind to all interfaces (http port 80).

Now following the doc for both apache and squid configuration works.

Note
NOTE:

NOT WORK the first line say error "Cant be transparent and cache in the same port!" the second line say: FATAL: Bundle in line x: cache_peer ..... this is for all next instructions and command for 2.6, all this need further investigation. Marco A. Barragan. sistemas@wi-fi.net.ve

Not working for dynamic pages
I'm using Squid 2.5, Memcached, MW 1.11. The non-static wiki pages are never cached while images are cached correctly (the access.log gives a HIT on them). My squid.conf follows the instructions of this page. Any suggestions?

This article really needs to be overhauled for 2.6
It is simply outdated and the code examples given do not work as of December 2, 2008. - Anonymous

I added "originserver" to the cache_peer line, without it squid will think the webserver is a cache peer and do all kinds of crazy stuff like asking it for digests.

About upload
I wanna know which files or functions handle the upload stuff. I mean how could my wiki choose one server to upload.Could I do some setting to change the path to upload? If anyone know anything about it,please let me know. thanks 125.33.196.169 04:02, 18 June 2009 (UTC)

2.7
The configuration for 2.6 doesn't work for 2.7, squid gives an error "ACL name 'all' not defined! FATAL bungled squid.conf line 6: cache_peer_access wiki deny all". Any hint?

DonPaolo 22:43, 15 February 2010 (UTC)
 * Add

acl all src 0.0.0.0/0.0.0.0 seems to help a bit, but other issues still remain for me. cariaso 27 Feb 2011

documentation is confusing for 2.6
The documentation is confusing for 2.6. There are two different 2.6 sections that show conflicting ways of setting it up. It also never mentions whether the configuration info given is supposed to overwrite certain parts of squid's default config file, or if it should go into a completely new config file. Can someone please upload a FULL working configuration file for 2.6 to reference? I think it would help a lot to have a full example.