You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The exact error described in #715 still appears to be happening in some cases. I am running v0.8.0 but ran into the same issue on master.
See below for a reduced case that fully reproduces the error. What's interesting is removing the call to request and inlining that logic into main makes the problem go away.
The Client is reusing the socket, since the server responded with keep-alive. This is not a bug.
The server is sending an extra \n after the end of the first response, and so when the hyper starts to parse the second response, it first sees the stray \n. hyper's parser knows to skip empty lines when handling server requests, but it seems that it was not included in client responses.
I'll fix it in the httparse crate, and since it's a bug fix, you'll be able to just cargo update to receive it.
The exact error described in #715 still appears to be happening in some cases. I am running v0.8.0 but ran into the same issue on master.
See below for a reduced case that fully reproduces the error. What's interesting is removing the call to
request
and inlining that logic intomain
makes the problem go away.The text was updated successfully, but these errors were encountered: