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
I wrote a module to process the problem
ena.https://github.com/flygoast/ngx_http_types_filter
our configuration in production like this:
location / {
types_filter $uri;
..
proxy_pass http://down_server;
}
At 2014-08-09 10:34:06,manish-ezest wrote:
>Hello Wandenberg,
>
>Yes, t
Hello!
On Fri, Aug 08, 2014 at 10:49:15PM -0400, manish-ezest wrote:
> Hello Maxim,
>
> The server_name(website) is a dummy name as I don't want to disclose the
> site name. I might have mistaken while editing the name. But I ensure you
> that the logs I have provided is correct. I am pasting my
Hello!
On Sat, Aug 09, 2014 at 02:19:32PM -0400, mastercan wrote:
> Hello,
>
> I've tried to use "fastopen" in the listen directive but nginx gave me an
> error that the option is unkown.
>
> I'm using nginx 1.7.4 on Debian Wheezy 3.14.13 kernel.
>
> I've compiled nginx myself.
> When I run th
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
Hello,
I've tried to use "fastopen" in the listen directive but nginx gave me an
error that the option is unkown.
I'm using nginx 1.7.4 on Debian Wheezy 3.14.13 kernel.
I've compiled nginx myself.
When I run the configure command, I get:
"checking for TCP_FASTOPEN ... not found"
'cat /proc/sys/
I have a freebsd server running two jails on one jail i have nginx and and
on the other jail i am running a node.js application.
Here is the nginx.conf file:
https://gist.github.com/nkhine/f620f8bdc0fb613b7b59
when viewing the site, every other request seems to time out and i get `The
connection
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;
