Heroku : sock=client at=warning code=H27 desc=”Client Request Interrupted”

H27 – Client Request Interrupted

The client socket was closed either in the middle of the request or before a response could be returned. For example, the client closed their browser session before the request was able to complete.

2010-10-06T21:51:37-07:00 heroku[router]: sock=client at=warning code=H27 desc="Client Request Interrupted" method=POST path="/submit/" host=myapp.herokuapp.com fwd=17.17.17.17 dyno=web.1 connect=1ms service=0ms status=499 bytes=0

Words from Heroku Dev Center

New HTTP Error code: H27 – Client Request Interrupted

Change effective on 03 June 2015

We’re rolling out a change that introduces a new error code: H27 - Client Request Interrupted.

This error will be logged if the client socket was closed either in the middle of the request or before a response could be returned.

2010-10-06T21:51:37-07:00 heroku[router]: at=error code=H27 desc="Client Request Interrupted" method=POST path="/submit/" host=myapp.herokuapp.com fwd=17.17.17.17 dyno=web.1 connect=1ms service=0ms status=499 bytes=0 sock=client

Previously, this error condition caused an H18 to be logged and the sock field could be used to differentiate between what are now H18 and H27 errors. The sock field remains on H18 errors for backwards compatibility, but will always have the value backend.

 

 

Copied from

https://devcenter.heroku.com/changelog-items/662

https://devcenter.heroku.com/articles/error-codes#h27-client-request-interrupted

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s