As far as specifications are required, the question above should be divided into a couple of answers:
- When browsers need to send an Origin header
- When browsers must internally set the origin of the Thatll value to get serialized in
null
I doubt that what Firefox requires for this (where it differs from the specification) is listed. But as for the listing of specification requirements, here they are, in all details, divided into two parts:
When browsers need to send an Origin header
Origin? is: Origin , Fetch CORS:
CORS- - HTTP- Origin. CORS, Origin , GET HEAD.
Fetch, , Origin , GET HEAD:
CORS httpRequests GET HEAD, Origin/httpRequests origin, serialized UTF-8 httpRequests.
Origin POST , POST ( Fetch "CORS " - Theyre ).
. , Fetch , , 2016-12-09. :
Origin POST-Origin POST <form> ( CORS)
, Firefox, , , , , .
, Origin , " CORS", , HTTP (S) , websocket, - navigate, websocket, same-origin no-cors.
XHR cors. API Fetch mode init-object fetch(…):
fetch("http://example.com", { mode: 'no-cors' })
crossorigin ( " CORS) HTML , cors ( Origin).
, (, , , -), no-cors, , Origin .
, Origin.
, null.
origin , null
, Origin , null, :
HTML :
, , ( "" ASCII- ), .
, , HTML , null.
HTML , :
- (
img ) - (
video audio) - ,
data: URL iframe sandbox allow-same-origin- ,
createDocument() .. - ,
- ,
- ?
Fetch , " " ( , " ", null …) :
URL , :
blob: URLfile: URL- URL,
http, https, ftp, ws, wss gopher.
, , , null - , Origin . , , Origin.