| From | Sent On | Attachments |
|---|---|---|
| Joel Eidsath | Jul 14, 2011 11:32 am | |
| Sirsiwal, Umesh | Jul 14, 2011 11:42 am | |
| Joel Eidsath | Jul 14, 2011 11:46 am |
| Subject: | Re: Nested error_page request | |
|---|---|---|
| From: | Sirsiwal, Umesh (usir...@verivue.com) | |
| Date: | Jul 14, 2011 11:42:23 am | |
| List: | ru.sysoev.nginx | |
Hey Joel,
You may want to look at: recursive_error_pages on;
-Umesh On Jul 14, 2011, at 2:33 PM, Joel Eidsath wrote:
Hello,
I'm trying to figure a way around a nested error_page request (which doesn't seem to work). The problem is that I've got a memcached setup that looks like this:
server {
error_page 500 502 /site_media/flat/500.html; proxy_intercept_errors on;
<snip>...
location / { <snip>... set $memcached_key "http://domain.com$uri"; memcached_pass <IP>:<PORT>; error_page 404 502 = @cache_miss; }
location @cache_miss { proxy_pass http://backend; } }
The cache_miss error_page directive seems to disable my ability to set a second error_page for 500 errors that then come from the backend. Is there a way that I can make this work, either by modifying my memcached setup or my error_page setup?
Joel
_______________________________________________ nginx mailing list ngi...@nginx.org http://nginx.org/mailman/listinfo/nginx
_______________________________________________ nginx mailing list ngi...@nginx.org http://nginx.org/mailman/listinfo/nginx





