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

test (do not merge) #333

Closed
wants to merge 3 commits into from
Closed

test (do not merge) #333

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
49421e5
test (do not merge)
jeremyroman Sep 6, 2024
ecc1aff
.
jeremyroman Sep 6, 2024
08819e7
.
jeremyroman Sep 6, 2024
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
2 changes: 2 additions & 0 deletions no-vary-search.bs
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -45,6 +45,8 @@ spec: RFC8941; urlPrefix: https://www.rfc-editor.org/rfc/rfc8941.html

<h2 id="status-and-venue">Status and venue note</h2>

t e s t ?

This document is being written as a web-style specification in the WICG for now, because that's the tooling and venue the author is familiar with. Its purpose is to nail down some details of the processing model in order to make writing and testing prototypes easier.

In the longer term, we envision this header being specified in a HTTPWG RFC, alongside whatever portion of the processing model can be shared among its various consumers. (That is, between both web platform specifications such as [[FETCH]], and HTTP specifications such as future modifications to [[RFC9111]].) It's just incubating in WICG for now.
Expand Down