Action caching and server aliases

rubyonrails-talk
1

I'm having some trouble with caching (namely expiring action caches) on my production server:

I have a site that can be accessed by both domain.com and www.domain.com. The problem is that pages cached through action caching are being put into both myapp/tmp/cache/domain.com and myapp/tmp/cache/ www.domain.com. So when it comes to expiring those actions, depending on how the site is being accessed, only part of the actions are expired (either in myapp/tmp/cache/domain.com or myapp/tmp/cache/ www.domain.com, but not both).

Is there some config variable I can set in environment.rb to omit the hostname from the caching mechanism? The API documentation seems sparse in this regard.

Thanks!

2

Is there some reason you're using both domains? I'd setup a web server redirect for one domain to the other so you don't split your google PR over 2 domains.

3

Thanks, Rick - of course that's the correct solution.

4

I'm having some trouble with caching (namely expiring action caches) on my production server:

I have a site that can be accessed by both domain.com andwww.domain.com. The problem is that pages cached through action caching are being put into both myapp/tmp/cache/domain.com and myapp/tmp/cache/ www.domain.com. So when it comes to expiring those actions, depending on how the site is being accessed, only part of the actions are expired (either in myapp/tmp/cache/domain.com or myapp/tmp/cache/ www.domain.com, but not both).

Is there some config variable I can set in environment.rb to omit the hostname from the caching mechanism? The API documentation seems sparse in this regard.

Is there some reason you're using both domains? I'd setup a web server redirect for one domain to the other so you don't split your google PR over 2 domains.

Thanks, Rick - of course that's the correct solution.

Be sure to use 301 redirects. Google *hates* 302.

-philip