Skip to content

Editorial: replace RFC7231 reference with RFC9110 #415

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

Merged
merged 1 commit into from
Nov 25, 2025
Merged

Editorial: replace RFC7231 reference with RFC9110 #415

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions index.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -142,8 +142,8 @@ <h2>
provide compatible semantics.
</p>
<p>
The <code><dfn>Content-Encoding</dfn></code> HTTP header, described in Section 3.1.2.2 of
[[RFC7231]], indicates the content coding applied to the payload of a <a>push message</a>.
The <code><dfn>Content-Encoding</dfn></code> HTTP header, described in Section 8.4 of
[[RFC9110]], indicates the content coding applied to the payload of a <a>push message</a>.
</p>
</section>
<section>
Expand Down