Hello!
On Thu, Feb 19, 2015 at 12:11:58PM -0600, Kunal Pariani wrote:
> Can you please tell me other such cases where this could happen ?
E.g., this can also happen when using an upstream{} with keepalive
connections cache configured.
> Can't think of any in my scenario atleast.
It's only who
Can you please tell me other such cases where this could happen ? Can't think
of any in my scenario atleast.
Thanks
-Kunal
- Original Message -
From: "Maxim Dounin"
To: nginx@nginx.org
Sent: Thursday, February 19, 2015 9:23:16 AM
Subject: Re: $upstream_addr containing th
Hello!
On Thu, Feb 19, 2015 at 08:49:33AM -0800, Kunal Pariani wrote:
> I have just one server configured with a single Ip address but I still see
> this.
The example case mentioned isn't the only case when this can
happen legitimately.
--
Maxim Dounin
http://nginx.org/
_
I have just one server configured with a single Ip address but I still see
this.
Thanks
-Kunal
On Feb 19, 2015 5:05 AM, "Maxim Dounin" wrote:
> Hello!
>
> On Wed, Feb 18, 2015 at 09:03:47PM -0600, Kunal Pariani wrote:
>
> > Hello,
> > I have just 1 backend server being reverse-proxied through ng
Hello!
On Wed, Feb 18, 2015 at 09:03:47PM -0600, Kunal Pariani wrote:
> Hello,
> I have just 1 backend server being reverse-proxied through nginx. The access
> log lists this one request for which the $upstream_addr has the same ip:port
> twice. Is this a bug ?
>
> :::10.255.255.248:5194
Hello,
I have just 1 backend server being reverse-proxied through nginx. The access
log lists this one request for which the $upstream_addr has the same ip:port
twice. Is this a bug ?
:::10.255.255.248:51947 - - [18/Feb/2015:19:52:43 -0600] "GET / HTTP/1.1"
302 454 "-" "Mozilla/5.0 (Macin
