GitLab

It makes authentication fail in some sites

Also use a different message for the following request to ensure
we don't get any cached information.

It's now only used for proxying.

This is what http1 does, so probably what users expect.

And stop allowing a null parent stream in SoupBodyInputStreamHttp2

This reverts commit d58335ed.

STATE_ERROR is set but never checked and I don't see how io message
error can be alive after the io finished, so store a GError in every
message io data struct instead.

In HTTP/2 we don't really need to read the rest of the response body to
complete the IO, we can just reset the stream.

This is only used by the client stream when it's closed. We are never
interested in the data read, we just want to skip it.

In case of cancellation, we destroy the io data for the message but the
session keeps processing the stream.

It seems to be problematic to read from there and I don't think it's
really needed.

We don't need to get it from the message when we already have it.

We consider it's in progress if we have io data for the given message in
both http1 and http2

To log the debug messages using g_log with domain "nghttp2"