# Client closed prematurely connection while reading client request line

**URL:** <https://www.ruby-forum.com/t/client-closed-prematurely-connection-while-reading-client-request-line/213136>\
**Category:** NGINX\
**Created:** [October 24, 2011, 11:06pm UTC](https://www.ruby-forum.com/t/client-closed-prematurely-connection-while-reading-client-request-line/213136 "2011-10-24T23:06:25Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![luislavena](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/l/0ea827/32.png) [@luislavena](https://www.ruby-forum.com/u/luislavena)\
**Post date:** [October 24, 2011, 11:06pm UTC](https://www.ruby-forum.com/t/client-closed-prematurely-connection-while-reading-client-request-line/213136/1 "2011-10-24T23:06:25Z")

</div>

Very basic configuration, strictly for serving static files.

I’ve got the error\_log setting configured to “info” to get more  
information  
as to what’s happening with connections, etc.

While monitoring the error log and loading a single static html file  
through  
my web browser, I noticed this line in the error log show up:

2011/10/24 16:02:04 [info] 26517#0: \*3132 client closed prematurely  
connection while reading client request line, client: ###.###.###.###,  
server: localhost

What’s the reason for this error, does it matter and is there a way to  
address it? is it indicative of a deeper network configuration issue  
with  
TCP settings?

Thanks

---

<div class="post-metadata">

**Author:** ![iberci](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/i/a3d4f5/32.png) [@iberci](https://www.ruby-forum.com/u/iberci)\
**Post date:** [October 25, 2011, 12:34am UTC](https://www.ruby-forum.com/t/client-closed-prematurely-connection-while-reading-client-request-line/213136/2 "2011-10-25T00:34:04Z")

</div>

Hello!

On Mon, Oct 24, 2011 at 05:06:03PM -0400, Ilan B. wrote:

> server: localhost
> 
> What’s the reason for this error, does it matter and is there a way to  
> address it? is it indicative of a deeper network configuration issue with  
> TCP settings?

Some modern browsers tend to open 2 tcp connections to server from  
start, and if you are loading a single static file - one of them  
remains unused. The browser eventually closes it without sending  
any request, and this causes the above message in logs.

Maxim D.