I just tried a quick test, using your first method for users/guests , with 419 instead of 418. Seems to work fine. Any reason I couldn't or shouldn't use these codes to redirect to different interal @locations???by paul2791 - Nginx Mailing List - English
Maxim, Thats brilliant, thanks Would proxy_pass be considered as a rewrite and safe within an IF as i use it a lot to bypass cache? Also, 418 is great code, had never seen that before. I do have some logic elsewhere in my conf where i have more than two ifs. Does Nginx allow the use of nondefined codes? 419 for instance? so i could have location / { error_page 418 = @cache1; error_pageby paul2791 - Nginx Mailing List - English
I've been trying to set up two separate proxy caches, one for logged in users, one for guests. The one for guests had a very long expiry as guest pages don't change much, User pages are very dynamic and expiry is very short. Using cookies i can tell if a page request is by a user or guest, but I cannot see any easy way to alter the proxy as all the proxy_cache commands can't be put inside an ifby paul2791 - Nginx Mailing List - English
I've been trying to set up two separate proxy caches, one for logged in users, one for guests. The one for guests had a very long expiry as guest pages don't change much, User pages are very dynamic and expiry is very short. Using cookies i can tell if a page request is by a user or guest, but I cannot see any easy way to alter the proxy as all the proxy_cache commands can't be put inside an ifby paul2791 - How to...