Skip to content
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

Jump to bottom

net/http: new status code: 103, Early Hints, RFC8297 #29655

Closed
vkuzmin-uber opened this issue Jan 10, 2019 · 3 comments
Closed

net/http: new status code: 103, Early Hints, RFC8297 #29655

vkuzmin-uber opened this issue Jan 10, 2019 · 3 comments
Labels
FrozenDueToAge NeedsFix The path to resolution is known, but the work has not been done.
Milestone
Go1.13

Comments

@vkuzmin-uber
Copy link
Contributor

What version of Go are you using (go version)?

go version go1.11.4 darwin/amd64

Does this issue reproduce with the latest release?

Yes

What operating system and processor architecture are you using (go env)?

darwin, OS X

What did you do?

Looked at net/http/status.go for available StatusCode constants. http package has HTTP status code from https://www.iana.org/assignments/http-status-codes/http-status-codes.xhtml

This doc was updated recently and new Informational code was added:
103 | Early Hints | [RFC8297]

Need to update http package as well.

What did you expect to see?

All latest HTTP codes, namely Early Hints

What did you see instead?

No 103, Early Hints
@vkuzmin-uber
Copy link
Contributor Author

I will publish code review

@gopherbot
Copy link

Change https://golang.org/cl/157339 mentions this issue: net/http: new status code: 103, Early Hints

@ALTree ALTree added this to the Go1.13 milestone Jan 10, 2019
@ALTree ALTree added the NeedsDecision Feedback is required from experts, contributors, and/or the community before a change can be made. label Jan 10, 2019
@bradfitz bradfitz added the NeedsFix The path to resolution is known, but the work has not been done. label Jan 11, 2019
@gopherbot gopherbot removed the NeedsDecision Feedback is required from experts, contributors, and/or the community before a change can be made. label Jan 11, 2019
@vkuzmin-uber
Copy link
Contributor Author

As I understand, go 1.12 was release. I guess CL can be merged now.

@rsc rsc mentioned this issue Jun 27, 2019
Closed
@golang golang locked and limited conversation to collaborators Feb 29, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
FrozenDueToAge NeedsFix The path to resolution is known, but the work has not been done.
Projects
None yet
Milestone
Go1.13
Development

No branches or pull requests
4 participants
@bradfitz @ALTree @gopherbot @vkuzmin-uber