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 Chat (such as one of these permanent autoconfirmed members).
HTTP Fetch Policy: Difference between revisions
(→Request: add credentials) |
|||
| Line 32: | Line 32: | ||
Headers: Also Content-Type with value application/json | Headers: Also Content-Type with value application/json | ||
Credentials: none (although the current draft says to include all) | |||
=== WebSocket cross-origin (no preflight) allowance === | === WebSocket cross-origin (no preflight) allowance === | ||
Latest revision as of 19:35, 23 March 2013
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).
- Everything else works within the syntax constraints.
Author headers: Everything but setRequestHeader() limitations.
Headers: Host, Origin, ...
Credentials: Cookies and HTTP authentication
Body: No limitations
Additional general cross-origin (no preflight) limitations
Methods: Only GET, HEAD, and POST.
Author 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
Headers: Also Last-Event-ID
CSP cross-origin (no preflight) allowance
Headers: Also Content-Type with value application/json
Credentials: none (although the current draft says to include all)
WebSocket cross-origin (no preflight) allowance
Headers: Also Upgrade: websocket, Connection: Upgrade, Sec-WebSocket-Key, Sec-WebSocket-Protocol, Sec-WebSocket-Version
Credentials: No HTTP authentication (due to API)
Response
...