Oh... thank you very much, Francis - I don't undestand how could I overlook
this, please don't hit me hard :)
Though it is introduced only in 1.7.1, but $upstream_http_* is indeed there
for older versions - perhaps, I am too tired so I missed it...
Posted at Nginx Forum:
http://forum.nginx.org/r
Francis, I know about no_cache and bypass - question is how to extract
*specific* cookie from the *response* (upstream reply), not the *request*.
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,250345,250347#msg-250347
___
nginx mailing list
n
Hi,
I am trying to make caching selective based on cookies set by upstream.
Example: worpress sets wordpress_test_cookie for every page, thus preventing
caching of pages unless Set-Cookie headers are ignored. On the other hand,
ignoring Set-Cookie in general is bad idea, as in this case when othe
Francis, thank you for your time and looking through the source :)
Though I still consider this issue as a "bug" (either in documentation or in
consistence), what really matters is that understanding how it works is very
helpful, and you did the perfect job explaining this.
Hopefully, someone, so
Well, this is where I am lost a bit - documentation only says "replacement
string", and from my understanding this includes possible expansion of
variables (like everywhere else), and it doesn't mention (or I couldn't
find, at least) that rewrite target is normalized URI (or that variables
could be
Hi,
According to documentation, "location" matches only against URI path,
ignoring query string. However, after "rewrite", when using variables
containing "?" character (like $request_uri for illustration), query becomes
part of $uri:
location /src/ {
rewrite ^ /dst$request_uri;
}
location /
