Okay, I've got some more details on this event. I've changed the query params to zzzz=1 to secure my customers data but otherwise these are unmodified. So based on this I *think* they are sending a second request through right? Also, is 180140 a sequential connection number? What's the 4388#0 designator? Lastly which of these lines indicates a "new request" and also which meansby cpriest - Nginx Mailing List - English
I will, I've got the latest built now with --with-debug but I have to wait until this evening to install into production, I'll know more in a couple of days.by cpriest - Nginx Mailing List - English
Was it ever determined whether this was an issue with the logger or with double-connections? I'm getting double-log entries while using nginx as a load balancer in front of 3 other servers. For a double-log entry on nginx side, there are two individual log entries on the target servers. Any idea if my issue is related to this one?by cpriest - Nginx Mailing List - English
Why did that solve the problem for this individual? This doesn't really answer my question anyways, I'm trying to determine why it would be logging it twice, not how to get around the issue. The servers behind nginx are showing two connections...by cpriest - Nginx Mailing List - English
I have nginx setup as a load balancer to three servers. Is there *any* reason a request would hit the log file more than once unless there were actually more than one incoming (from the internet) requests? For example, if one of my internal servers is down or slow and a proxy timeout setting is reached, would that cause nginx to log twice to the access log? Would there be any message about saby cpriest - Nginx Mailing List - English