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

Merge the HTTP guidance into the "consult other specs" section. #546

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Merge the HTTP guidance into the "consult other specs" section. #546

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
32 changes: 6 additions & 26 deletions index.bs
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -78,6 +78,8 @@ urlPrefix: https://w3c.github.io/geolocation-api/; spec: geolocation
urlPrefix: https://html.spec.whatwg.org/multipage/; spec: HTML
url: system-state.html#dom-navigator-online; type: attribute; for: NavigatorOnline; text: onLine;
url: media.html#dom-media-play; type:method; for:HTMLMediaElement; text:play()
urlPrefix: https://www.rfc-editor.org/rfc/rfc9110.html; spec: rfc9110
url: #name-accept; type: http-header; text: Accept
urlPrefix: https://w3c.github.io/remote-playback/; spec: REMOTE-PLAYBACK
url: #remoteplayback-interface; type:interface; text: RemotePlayback
url: #dfn-remote-playback-devices; type:dfn; text: remote playback device
Expand Down Expand Up @@ -561,9 +563,11 @@ An incomplete list of such guidance follows:

* [[encoding#specification-hooks|Encoding]]
* [[fetch#fetch-elsewhere|Fetch]]
* [[RFC9205 inline]],
especially on [[RFC9205#section-4.7|defining header fields]], and
[other HTTP RFCs](https://datatracker.ietf.org/doc/search?name=HTTP&sort=&rfcs=on&by=group&group=httpbis)
* [[hr-time#sec-tools|Time]]
* [[url#url-apis-elsewhere|URLs]]
* [[#using-http]]

Consult with the relevant community
when using their specification.
Expand Down Expand Up @@ -1107,7 +1111,7 @@ even if this means using another character to separate values.
<div class=example>

The <{input/accept}> attribute is a comma-separated list of values,
because it needs to match the syntax of the `Accept` HTTP header. (See [[#using-http|guidance on HTTP headers]])
because it needs to match the syntax of the [:Accept:] HTTP header.

</div>

Expand Down Expand Up @@ -3136,30 +3140,6 @@ due to security implications, and instead recommend enforcing strict MIME types

New MIME types should have a specification and should be registered with the Internet Assigned Numbers Authority (IANA).

<h3 id="using-http">Consult documentation on best practices when using HTTP</h3>

When using [[RFC9110|HTTP]],
consult [[RFC9205 inline]]
for advice on correct usage of the protocol.

[Fetch](https://fetch.spec.whatwg.org/) is the way that
user agents most often interact with servers.
Fetch defines the CORS protocol and necessary security checks.
Outside of those constraints necessary for security,
Fetch does not provide guidelines on how to best use HTTP.
Appropriate use of methods, header fields, content types, caching, and other HTTP features
might need to be defined.

Recommendations on best practices for HTTP
can be found in [[RFC9205 inline]] and
[other HTTP RFCs](https://datatracker.ietf.org/doc/search?name=HTTP&amp;sort=&amp;rfcs=on&amp;by=group&amp;group=httpbis).
RFC 9205 includes advice on
[[RFC9205#section-4.3|specifying client behavior]],
[[RFC9205#section-4.7|defining header fields]],
[[RFC9205#section-4.8|use of media types]],
[[RFC9205#section-4.16|evolving specifications]], and
other advice on how to get the most out of HTTP.

<h3 id="extend-manifests">Extend existing manifest files rather than creating new ones</h3>

If your feature requires a manifest,
Expand Down
Loading