Sean McArthur
Sean McArthur
I think there's also a maintenance cost to separating them. Keeping it in-crate allows other internal parts to access private details. Is there another thing that you hope to gain?...
So first off, here's the informational status codes, just so we know what we're dealing with: - **100 Continue**: Should be sent if the client sends `Expect: 100-continue` before sending...
In that case, for the client, I'd probably put the informational status codes on a separate pollable method, since they are only informational, and unless I specifically want to handle...
According to [HTTP/1.1](https://tools.ietf.org/html/rfc7231#section-6.2): > A user agent MAY ignore unexpected 1xx responses. HTTP2 doesn't define any additional semantic value to 1xx status codes.
@inikulin I'd say the first step would be to update `h2` to accept headers frames with a 1xx status code and at least ignore them, for now. That would make...
The description mentions not requiring an authority, but it looks like this changes it to stop checking if the provided authority is valid. So, in the Unix socket case, does...
Relevant part of the spec: http://httpwg.org/specs/rfc7540.html#discover-http
@lucab probably not that issue specifically in hyper, but for h2, it wouldn't matter what created the connection and did the HTTP/1 request and received the 101 response, but after...
cc @piscisaureus
Should this actually be done at this level? You could imagine a request with useful info sent, but the client doesn't want the response at all, and so sends a...