-
Notifications
You must be signed in to change notification settings - Fork 18k
x/net/http2: unexpected custom errors when HTTP2.0 PUT request gets lesser content than the specified content-length #30648
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
Labels
FrozenDueToAge
WaitingForInfo
Issue is not actionable because of missing required information, which needs to be provided.
Comments
harshavardhana
added a commit
to harshavardhana/minio
that referenced
this issue
Mar 7, 2019
We should internally handle when http2 input stream has smaller content than its content-length header Upstream issue reported golang/go#30648 This a change which we need to handle internally until Go fixes it correctly, till now our code doesn't expect a custom error to be returned.
8 tasks
harshavardhana
added a commit
to harshavardhana/minio
that referenced
this issue
Mar 7, 2019
We should internally handle when http2 input stream has smaller content than its content-length header Upstream issue reported golang/go#30648 This a change which we need to handle internally until Go fixes it correctly, till now our code doesn't expect a custom error to be returned.
harshavardhana
added a commit
to harshavardhana/minio
that referenced
this issue
Mar 7, 2019
We should internally handle when http2 input stream has smaller content than its content-length header Upstream issue reported golang/go#30648 This a change which we need to handle internally until Go fixes it correctly, till now our code doesn't expect a custom error to be returned.
harshavardhana
added a commit
to harshavardhana/minio
that referenced
this issue
Mar 7, 2019
We should internally handle when http2 input stream has smaller content than its content-length header Upstream issue reported golang/go#30648 This a change which we need to handle internally until Go fixes it correctly, till now our code doesn't expect a custom error to be returned.
An example would help. |
harshavardhana
added a commit
to harshavardhana/minio
that referenced
this issue
Mar 7, 2019
We should internally handle when http2 input stream has smaller content than its content-length header Upstream issue reported golang/go#30648 This a change which we need to handle internally until Go fixes it correctly, till now our code doesn't expect a custom error to be returned.
will do @fraenkel |
harshavardhana
added a commit
to harshavardhana/minio
that referenced
this issue
Mar 7, 2019
We should internally handle when http2 input stream has smaller content than its content-length header Upstream issue reported golang/go#30648 This a change which we need to handle internally until Go fixes it correctly, till now our code doesn't expect a custom error to be returned.
harshavardhana
added a commit
to harshavardhana/minio
that referenced
this issue
Mar 7, 2019
We should internally handle when http2 input stream has smaller content than its content-length header Upstream issue reported golang/go#30648 This a change which we need to handle internally until Go fixes it correctly, till now our code doesn't expect a custom error to be returned.
harshavardhana
added a commit
to harshavardhana/minio
that referenced
this issue
Mar 7, 2019
We should internally handle when http2 input stream has smaller content than its content-length header Upstream issue reported golang/go#30648 This a change which we need to handle internally until Go fixes it correctly, till now our code doesn't expect a custom error to be returned.
harshavardhana
added a commit
to minio/minio
that referenced
this issue
Mar 8, 2019
We should internally handle when http2 input stream has smaller content than its content-length header Upstream issue reported golang/go#30648 This a change which we need to handle internally until Go fixes it correctly, till now our code doesn't expect a custom error to be returned.
Timed out in state WaitingForInfo. Closing. (I am just a bot, though. Please speak up if this is a mistake or you have the requested information.) |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
FrozenDueToAge
WaitingForInfo
Issue is not actionable because of missing required information, which needs to be provided.
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
Yes with go1.12
What operating system and processor architecture are you using (
go env
)?go env
OutputWhat did you do?
Set a high content-length and send shorter data leads to unexpected errors reported by the server
Should be ideally
What did you expect to see?
Expected to see io.ErrUnexpectedEOF
What did you see instead?
This behavior differs from HTTP 1.1 behavior.
The text was updated successfully, but these errors were encountered: