Shell Makefile
Latest commit e4cf6c4 Jan 19, 2017 @annevk annevk committed on GitHub Only set Access-Control-Request-Headers when its value is non-empty
This is how it used to be in the now-obsolete CORS specification. What the Fetch Standard said before this commit is causing subtle issues on servers.

Tests: w3c/web-platform-tests#4556.

Fixes #459.

This repository hosts the Fetch Standard.

Code of conduct

We are committed to providing a friendly, safe and welcoming environment for all. Please read and respect the WHATWG Code of Conduct.

Contribution opportunities

Folks notice minor and larger issues with the Fetch Standard all the time and we'd love your help fixing those. Pull requests for typographical and grammar errors are also most welcome.

We'd be happy to mentor you through this process. If you're interested and need help getting started, leave a comment on the issue or ask around on IRC.

Pull requests

In short, change and submit your patch, with a good commit message. Consider reading through the WHATWG FAQ if you are new here.

Please add your name to the Acknowledgments section in your first pull request, even for trivial fixes. The names are sorted lexicographically.

If you want to preview the spec locally, you can either use a locally installed copy of Bikeshed by running make or use the HTTP API version by running make remote.

If you want to do a complete "local deploy" including commit and/or branch snapshots, run

./ --local


Use a column width of 100 characters.

Do not use newlines inside "inline" elements, even if that means exceeding the column width requirement.

 <a href=>set <var>response</var>'s CSP list</a>
 on <var>response</var>. <span data-anolis-ref>CSP</span>

is okay and

 <a href=>set <var>response</var>'s CSP
 list</a> on <var>response</var>. <span data-anolis-ref>CSP</span>

is not.

Using newlines between "inline" element tag names and their content is also forbidden. (This actually alters the content, by adding spaces.) That is


is fine and


is not.

An <li> element always has a <p> element inside it, unless it's a child of <ul class=brief>.

If a "block" element contains a single "block" element, do not put it on a newline.

Do not indent for anything except a new "block" element. For instance

 <li><p>Set <var>response</var>'s <span title=concept-response-url-list>url list</span> to a copy of
 <var>request</var>'s <span title=concept-request-url-list>url list</span>.

is not indented, but

  <p>Run these substeps <span data-anolis-spec=html>in parallel</span>:



End tags must be omitted when possible and attribute values must not be quoted (if necessary, use double quotes).

Merge policy

If you can commit to this repository, see the html repository's TEAM for guidelines.


Tests can be found in the fetch/ directory of the web-platform-tests repository.