Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unexpected end of input #68

Open
benmerckx opened this issue Dec 18, 2016 · 0 comments
Open

Unexpected end of input #68

benmerckx opened this issue Dec 18, 2016 · 0 comments

Comments

@benmerckx
Copy link
Member

benmerckx commented Dec 18, 2016

The secure tcpclient works in most cases. But I've found a few where the server would reply with either:

  • 503 Service Unavailable
  • 422 Unexpected end of input

I've also noticed the 422 error in two cases while using the tcpclient. The only workaround I've found so far is disabling the cnx.sink.close() call after body and headers are sent, which I think should signal the end of the request, and by adding extra headers (connection: close and content-length: 0).

I don't really have a clue why this happens or how to properly solve it, any ideas are welcome :) In all cases the (Secure)StdClient did work, but since it buffers the whole body (#67) it's not suitable for my needs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant