This solution would really help .
Thanks a lot for the info .. :)
Regards
Shobhit Mishra
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,250307,250341#msg-250341
___
nginx mailing list
nginx@nginx.org
Hi all,
I'm trying to understand why the use of this configuration code does not
work:
location ^~ /setup {
auth_basic Restricted Access;
auth_basic_user_filehtpasswd;
try_files $uri $uri/ /setup/index.php?$uri$args;
On Sun, May 25, 2014 at 05:49:33AM -0400, TECK wrote:
Hi there,
I'm trying to understand why the use of this configuration code does not
work:
Answer #1: what does does not work mean?
What request do you make; what response do you get; what response do
you want?
try_files
hi:
In man epoll , a section refer to epoll edge trigger starvation
problem, and around to this we need to maintain a ready list instead of
read socket
until EAGAIN. but i didn't find any related solution code in nginx. In
request body read function `ngx_http_do_read_client_request_body`,
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
On Sun, May 25, 2014 at 02:19:16PM -0400, aldem wrote:
Hi there,
I am trying to make caching selective based on cookies set by upstream.
http://nginx.org/r/proxy_no_cache
Is this possible at all? I couldn't find anything (like variables) that
allows to examine response for this purpose.
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
On Sun, May 25, 2014 at 04:43:10PM -0400, aldem wrote:
Francis, I know about no_cache and bypass - question is how to extract
*specific* cookie from the *response* (upstream reply), not the *request*.
no_cache - yes.
bypass - no.
upstream reply - which part of
$upstream_cookie_name
cookie
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:
