Re: [Rails] max-age/header problems with nginx

The Sat, 18 Sep 2010 14:30:57 -0700 (PDT),
badnaam <asitkmishra@gmail.com> wrote:

> 0 down vote favorite
>
>
> I notice that in my production enviornment (where I have memcached
> implemented) in see a cache-control - max-age header in firebug,
> anytime I am looking at an index page (posts for example).
>
> Cache-Control max-age=315360000
>
> In my dev environment that header looks like following.
>
> Cache-Contro private, max-age=0, must-revalidate
>
> As far as I know I have not done anything special with my nginx.conf
> file to specify max age for regular content, I do have expires-max set
> for css, jpg etc. here is my nginx.conf file..
>
> http://pastie.org/1167080
>

Look more closely at your regex in your pastie :

location ~* ^.+.(jpg|jpeg|gif|png|css|js|swf)?([0-9]+)?$ {
expires max;
passenger_enabled on;
}

An expression is optional when followed by '?'

So your regex matches anything with at least 2 characters (.+ matches
one or more characters, and the following '.' matches one character,
the remaining is optional)

Happy regex hacking,

Lionel

--
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
To post to this group, send email to rubyonrails-talk@googlegroups.com.
To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.