Eugaia Wrote: ------------------------------------------------------- > saltyflorida wrote: > > saltyflorida Wrote: > > > -------------------------------------------------- > ----- > > > >> Eugaia Wrote: > >> > -------------------------------------------------- > >> ----- > >> > >>> saltyflorida wrotby saltyflorida - Nginx Mailing List - English
saltyflorida Wrote: ------------------------------------------------------- > Eugaia Wrote: > -------------------------------------------------- > ----- > > saltyflorida wrote: > > > I forgot to mention that I am using caching > with > > the HTTP Proxy module and that I only want to > > cache responses from the production servers. > When > &gby saltyflorida - Nginx Mailing List - English
Eugaia Wrote: ------------------------------------------------------- > saltyflorida wrote: > > I forgot to mention that I am using caching with > the HTTP Proxy module and that I only want to > cache responses from the production servers. When > I have the cookie set to "testing" or "staging", > I'd like to bypass the cache and talk directly to >by saltyflorida - Nginx Mailing List - English
Piotr Sikora Wrote: ------------------------------------------------------- > Eliot, > try using: proxy_cache_key > $my_cache_key$cookie_uslnn_env; > > Best regards, > Piotr Sikora < piotr.sikora@frickle.com > > > > _______________________________________________ > nginx mailing list > nginx@nginx.org > http://nginx.org/mailman/listinfo/ngiby saltyflorida - Nginx Mailing List - English
merlin corey Wrote: ------------------------------------------------------- > On Thu, Jan 28, 2010 at 4:24 PM, merlin corey > wrote: > > Marcus' solution should be just fine, but I feel > I must ask an > > important question: > > > > Doesn't it make more sense to have production, > static, and dev as > > separate server blocks entirely with theiby saltyflorida - Nginx Mailing List - English
Eugaia Wrote: ------------------------------------------------------- > Hi, > > saltyflorida wrote: > > Is it possible to switch backend clusters of > servers based on a cookie? > > > > I would like to set a cookie named "env" and do > something like this: > > > > if ($http_cookie ~* "env=testing(;|$)") > { &by saltyflorida - Nginx Mailing List - English
merlin corey Wrote: ------------------------------------------------------- > On Thu, Jan 28, 2010 at 4:03 PM, Marcus Clyne > wrote: > > Hi, > > > > saltyflorida wrote: > >> > >> Is it possible to switch backend clusters of > servers based on a cookie? > >> > >> I would like to set a cookie named "env" and do >by saltyflorida - Nginx Mailing List - English
Is it possible to switch backend clusters of servers based on a cookie? I would like to set a cookie named "env" and do something like this: if ($http_cookie ~* "env=testing(;|$)") { proxy_pass http://backend_testing; } if ($http_cookie ~* "env=staging(;|$)") { proxy_pass http://backend_staging; }by saltyflorida - Nginx Mailing List - English
I was wondering if anyone else is still having this problem of Nginx getting stuck in the UPDATING state after upgrading to the fixed version of Nginx. I saw this using Nginx 0.7.62 and I upgraded to 0.8.24 because I saw it had been fixed, but recently saw the problem again. Here is my configuration: proxy_cache_path /mnt/nginx_cache levels=1:2 keys_zone=one:10mby saltyflorida - Nginx Mailing List - English