13 messages in ru.sysoev.nginxClient closed keepalive connection
FromSent OnAttachments
Wilson BilkovichApr 27, 2007 10:39 am 
Igor SysoevApr 27, 2007 10:52 am 
Wilson BilkovichApr 27, 2007 11:11 am 
Igor SysoevApr 27, 2007 11:17 am 
Wilson BilkovichApr 27, 2007 11:22 am 
Igor SysoevApr 27, 2007 11:33 am 
Wilson BilkovichApr 27, 2007 11:46 am 
Cliff WellsApr 27, 2007 9:10 pm 
Igor SysoevApr 27, 2007 11:47 pm 
Wilson BilkovichApr 28, 2007 10:01 am 
Igor SysoevApr 28, 2007 11:46 am 
Wilson BilkovichApr 28, 2007 1:35 pm 
Igor SysoevApr 29, 2007 7:03 am 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:Client closed keepalive connectionActions...
From:Wilson Bilkovich (wils@public.gmane.org)
Date:Apr 27, 2007 10:39:17 am
List:ru.sysoev.nginx

I am having some difficulty with nginx as a load balancer on MacOS X (Intel). I am running 0.5.19, but the problem occurs with recent earlier versions as well.

With "use kqueue" 2007/04/26 22:26:15 [info] 4133#0: *3048 kevent() reported that client 192.168.0.100 closed keepalive connection

With "use poll" 2007/04/26 22:59:48 [info] 10189#0: *375 client 192.168.0.100 closed keepalive connection

On the client side, I get a "Socket closed." error. My HTTP client is not configured to use keepalive, which makes the error message seem very strange. The only 'weird' thing I am doing is sending a '100 Continue' response from the back-end server. Does nginx have different behavior when I send back a 100?

Thanks, --Wilson.