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

Comments

firebus’s picture

firebus commented

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

chadcrew’s picture

chadcrew commented

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

firebus’s picture

firebus commented

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.

asb’s picture

asb commented

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

mikeytown2’s picture

mikeytown2 commented
Status: Active » Closed (fixed)

Closing all 5.x issues; will only reevaluate if someone steps up #454652: Looking for a co-maintainer - 5.x

Reason is 6.x has 10x as many users as 5.x; also last 5.x dev was over a year ago. The 5.x issue queue needs to go.

asb’s picture

asb commented
Version: 5.x-1.x-dev » 6.x-1.x-dev
Status: Closed (fixed) » Active

Support request still applies for 6.x, re-opening.