-
Notifications
You must be signed in to change notification settings - Fork 322
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
Support 100 continue responses #592
Comments
Any feedback on this one, please? Thanks already. |
If I understand correctly, yes, that's something we should support. As far as I understand second response comes immediately after the 100 Continue - in other words 1 request, but 2 responses. Am I right? |
Indeed, it seems that we are receiving 2 responses from one request. I'll see to prepare a PR to support this 100 continue code. |
I've tried to add support for reading the second response and the only solution which I've found is a change in
It seems to be very hacky for me, and the response I've spent few hours more to find anything better, but it seems that
in Anyone is having any idea where we can put the logic to support this kind of scenario? For more context - in |
Realized that we should not listen for status complete event, instead handle message complete event in a special way. |
It seems that HTTP isn't following the
100-continue
responses:when cURL does:
I would expect the HTTP response to be
<HTTP::Response/1.1 200 OK {}>
.Is it something what the HTTP gem should support?
The text was updated successfully, but these errors were encountered: