On Sun, Aug 10, 2014 at 10:12:32AM +0530, Pankaj Kaushik wrote:
Hi there,
> I have understanding that $uri will be changed to actual uri when location
> block will be parsed.
Your understanding is wrong.
> why is it not happening?
Because your understanding is wrong.
> There are two scenario
Hey Francis,
> Your request is for "/". The only location block you have is a prefix
> match for the four-character string "$uri", which does not match
> your request, so the request is processed by the default server-level
> configuration.
>
>
I have understanding that $uri will be changed to a
On Sat, Aug 09, 2014 at 07:08:55PM +0530, Pankaj Kaushik wrote:
Hi there,
> Also when i checked the error log, the client request is not going to any
> upstream server. Instead it is routing to some default location.
> request: "GET / HTTP/1.1", host: "65.60.72.19:90"
> Why it is happening?
Yo
Hi,
Also when i checked the error log, the client request is not going to any
upstream server. Instead it is routing to some default location.
2014/08/09 06:31:55 [info] 32681#0: *2 client 14.102.112.84 closed
keepalive connection
2014/08/09 06:36:13 [notice] 329#0: signal process started
2014/08
Hi,
I am getting this error : ERROR: XmlParseFailure
Can anybody please let me know what is the issue?
Below is my nginx.conf.
map $uri $key2 {
~^(?/[^/]+)/ $key;
default "";
}
upstream backend {
hash $key2 consistent;
