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.

Sign up for GitHub

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

Change the defining document for HTTP from RFC7230 to RFC9110 #519

Closed
kalyanaj opened this issue Feb 14, 2023 · 2 comments · Fixed by #521
Closed

Change the defining document for HTTP from RFC7230 to RFC9110 #519

kalyanaj opened this issue Feb 14, 2023 · 2 comments · Fixed by #521
Assignees
@basti1302

Comments

@kalyanaj
Copy link
Contributor

This is feedback from the IETF HTTP WG:

"The defining document for HTTP is now RFC9110, not RFC7230/1; please update your references accordingly."
@kalyanaj
Copy link
Contributor Author

Re-assigning per our discussion in the WG meeting, thanks Bastian!

@basti1302
Copy link
Contributor

Per meeting: We probably want to make that change for level 2, but not backport it to level 1. Some research is required to check whether that change has any impact on our spec (it shouldn't)

basti1302 pushed a commit to instana/trace-context that referenced this issue Feb 27, 2023
update references to RFC7230 to RFC9110
dde7b2d 
This addresses feedback from the IETF HTTP WG: "The defining document
for HTTP is now RFC9110, not RFC7230; please update your references
accordingly."

The relevant sections in RFC9110 have no semantic changes in comparison
to RFC7230 that affect this specification.

fixes w3c#519
@basti1302 basti1302 mentioned this issue Feb 27, 2023
Merged
basti1302 pushed a commit that referenced this issue Feb 28, 2023
@basti1302
update references to RFC7230 to RFC9110
d7ad23a 
This addresses feedback from the IETF HTTP WG: "The defining document
for HTTP is now RFC9110, not RFC7230; please update your references
accordingly."

The relevant sections in RFC9110 have no semantic changes in comparison
to RFC7230 that affect this specification.

fixes #519
basti1302 pushed a commit to instana/trace-context that referenced this issue Feb 28, 2023
update references to RFC7230 to RFC9110
eacd824 
This addresses feedback from the IETF HTTP WG: "The defining document
for HTTP is now RFC9110, not RFC7230; please update your references
accordingly."

The relevant sections in RFC9110 have no semantic changes in comparison
to RFC7230 that affect this specification.

fixes w3c#519
@basti1302 basti1302 mentioned this issue Feb 28, 2023
Merged
basti1302 pushed a commit to instana/trace-context that referenced this issue Mar 14, 2023
update references to RFC7230 to RFC9110
e81c9a2 
This addresses feedback from the IETF HTTP WG: "The defining document
for HTTP is now RFC9110, not RFC7230; please update your references
accordingly."

The relevant sections in RFC9110 have no semantic changes in comparison
to RFC7230 that affect this specification.

fixes w3c#519
basti1302 pushed a commit that referenced this issue Mar 14, 2023
@basti1302
update references to RFC7230 to RFC9110
5058896 
This addresses feedback from the IETF HTTP WG: "The defining document
for HTTP is now RFC9110, not RFC7230; please update your references
accordingly."

The relevant sections in RFC9110 have no semantic changes in comparison
to RFC7230 that affect this specification.

fixes #519
@kalyanaj kalyanaj mentioned this issue Mar 28, 2023
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@basti1302 basti1302

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

update references to RFC7230 to RFC9110 instana/trace-context
2 participants
@basti1302 @kalyanaj