Anthony Ramine

Actually [the RFC](https://httpwg.org/specs/rfc7540.html#rfc.section.8.1.2.6) makes it clear that any premature end of stream is definitely a protocol error, my bad: > A request or response that includes a payload body can...

I'm curious though as to how a proxy making a h1 request to some origin on behalf of a h2 request it received from the client should handle the case...

It turns out that the hanging is probably due to the proxy or the client, so closing this.

Repurposed the issue.

I wonder if we should also expose the frames too large for the stream's window size, and those that overflow content-length.

@seanmonstar Do you have any opinion on how to implement this? My initial thought was to add a new `recv::Event::ContentOverflow` or something like that, which triggers a stream error when...

That's what I tried at first, but then that would mean resetting the stream `poll_data` when that new event is popped from the `pending_recv` queue, right?

It's changing a panic a bit. I'm trying to debug a bug we have at work about the assertion `self.window_size >= sz as usize` in `FlowControl::send_data` as described in https://github.com/hyperium/h2/issues/607....

> I believe that the solution is to add a new `Ignore` variant to [this](https://github.com/carllerche/h2/blob/master/src/codec/framed_read.rs#L37). Read the continuation frame & discard it. Link with a hash so it doesn't get...

I'm not sure how you would do that, like, how do you know that the underlying socket is an actual raw socket, without TLS, etc?