Squid
chadcrew - January 27, 2008 - 14:56
| Project: | Boost |
| Version: | 5.x-1.x-dev |
| Component: | Apache integration |
| Category: | support request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Jump to:
Description
Hi,
Thanks for the great module.
I was wondering if there would be a problem with putting a Squid reverse proxy cache in front of apache when using Boost. I tried it out and the performance benefit seemed to be huge - about 4x the number of requests with apache alone and very little memory usage under load. Could this cause any problems though? I will keep investigating and report back, but thought I would see if you had any insights.
Thanks,
Chad
#1
works for me with no issues.
note that squid respects the cache headers when determining what to cache, and the cache headers in the default boost config/htaccess is very very bad
#2
Thanks for your reply. I played around with it for a while and it seemed to work pretty well. I don't need it on the production server yet, so I can't comment on that. What about the boost config is bad for cache headers?
Best,
Chad
#3
see http://drupal.org/node/185075
the .htaccess that currently ships with boost will disable client side caching for all images, css files, javascript etc - all things you'd really like squid to cache.
#4
Hi,
That sounds most interesting!
Would anyone care to share his/her experiences in more detail, especially the Squid configuration (or have I missed another posting regarding Drupal + Squid + Boost).
Thanks & greetings, -asb