Document Actions
Simple "Squid on Windows" caching solution
This How-to applies to:
Any version.
This How-to is intended for:
Server Administrators
The intention of this text is to mention the simplest solution of caching a single Plone site, not to describe in details all about caching, proxy-ing, caching strategies, diferences between Apache and Squid caching, virtual hosting etc. There are many documents written about all these themes. Among others you can follow the links at the end of the text.
There are many TODOs about using Squid with Zope on Unix systems. They describe the product "SquidGuard" which can not be installed on a Windows system.
Therefore you can use "mappings" tab of "VirtualHostMonster", and then, the whole solution is Windows-based.
For example, my Squid and Zope are installed on the same Windows 2000 system, Squid on port 80 and Zope on port 8888.
My basic Squid configuration:
http_port 80
httpd_accel_port 8888
Find more about Squid configuration in the product "CacheFu".
Add a VirtualHostMonster In the root Zope folder, and in its mappings tab set:
127.0.0.1:8888/VirtualHostBase/http/my.domain.org:80
This directive directs all created links on new pages back through the port 80.
see also:
-
Squid integration pointers
- Some references to setting up Squid as a caching server in front of Zope.
-
Crash-Fu
- A crash-course in CacheFu, squid, http acceleration, and a ton of useful links.
-
Simple Plone Clustering with Squid and Pound
- A simple Squid/Pound/Zope setup. Now you can do it without rewrite rules or redirector scripts and take advantage of squid acceleration and the scalability of ZEO.
-
Proxying
- Some hints about the importance of running a caching proxy in front of Zope for performance reasons.
-
Cache Content
- How to change Plone's default cache settings so you can cache pages on your site.
