SocketException: Unexpected end of file from server

[Brian Brooks]

First, thanks for making webbit and webbit-rest.  It made building a rest application very easy.

Every 5-7 days my webbit-rest client keeps getting "SocketException: Unexpected end of file from server". At times I can also reproduce this issue by hitting the REST URL using a web browser (Chrome returns Unable to load the webpage because the server sent no data.Error code: ERR_EMPTY_RESPONSE). Some basic googling shows this error typically means that the Content-Length header is not set. Is this a known issue? Should I file a defect against webbit server rather than webbit-rest?

Most of the source code involved is in this issue I filed last week against webbit-rest.  No one has responded to that issue so far.

https://github.com/webbit/webbit-rest/issues/3

Sincerely,

Brian Brooks

[Brian Brooks]

On Tuesday, September 24, 2013 9:44:17 AM UTC-4, Brian Brooks wrote:

Every 5-7 days my webbit-rest client keeps getting "SocketException: Unexpected end of file from server". At times I can also reproduce this issue by hitting the REST URL using a web browser (Chrome returns Unable to load the webpage because the server sent no data.Error code: ERR_EMPTY_RESPONSE). Some basic googling shows this error typically means that the Content-Length header is not set. Is this a known issue? Should I file a defect against webbit server rather than webbit-rest?

Per @aslakhellesoy comment on webbit/webbit-rest#3, I've re-filed this issue against webbit rather than webbit-rest: https://github.com/webbit/webbit/issues/124.

Brian