A user account is required in order to edit this wiki, but we've had to disable public user registrations due to spam.

To request an account, ask an autoconfirmed user on IRC (such as one of these permanent autoconfirmed members).

HTTP Fetch Policy

From WHATWG Wiki
Revision as of 19:05, 23 March 2013 by Annevk (talk | contribs) (Created page with "This document tries to document the platform's fetching policy for HTTP. == Request == === General limitations === Methods: * Uppercased (so e.g. geT becomes GET): CONNECT...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

This document tries to document the platform's fetching policy for HTTP.

Request

General limitations

Methods:

  • Uppercased (so e.g. geT becomes GET): CONNECT, DELETE, GET, HEAD, OPTIONS, POST, PUT, TRACE, and TRACK.
  • Never work: CONNECT, TRACE, and TRACK (subset of the above).

Headers: Limitations as per setRequestHeader().

Body: No limitations

Additional general cross-origin (no preflight) limitations

Methods: Only GET, HEAD, and POST.

Headers: Only Accept, Accept-Language, Content-Language, and Content-Type. If Content-Type, value excluding parameters must be application/x-www-form-urlencoded, multipart/form-data, or text/plain.

EventSource cross-origin (no preflight) allowance(sp?)

Headers: Last-Event-ID

CSP cross-origin (no preflight) allowance(sp?)

Headers: Content-Type, with value application/json

Response

...