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

Cache lists HTTP/1.1 as a normative reference when it could be informative #911

Closed
royfielding opened this issue Jul 26, 2021 · 2 comments
Closed

Cache lists HTTP/1.1 as a normative reference when it could be informative #911

royfielding opened this issue Jul 26, 2021 · 2 comments
Assignees
@reschke
Labels
auth48 Issues to be fixed in AUTH48 (or before) caching editorial

Comments

@royfielding
Copy link
Member

We spent all that time removing normative references from Semantics to HTTP/1.1 and yet Cache has several "see other" kinds of references to HTTP/1.1 (for security considerations) and then lists it as normative reference.

I think this can be fixed by the RFC editor.
@mnot
Copy link
Member

mnot commented Jul 26, 2021

Odd. I know we did the work to enable this; did we just forget to actually change the reference type?

@reschke
Copy link
Contributor

reschke commented Jul 27, 2021

I prefer fixing things as early as possible. Also, more feedback might come in before approval...

@reschke reschke self-assigned this Jul 27, 2021
@reschke reschke added the auth48 Issues to be fixed in AUTH48 (or before) label Jul 27, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@reschke reschke

Labels
auth48 Issues to be fixed in AUTH48 (or before) caching editorial
Milestone
No milestone
Development

No branches or pull requests
3 participants
@mnot @reschke @royfielding