- Deal with authentication (URLs containing username/password, servers responding with 401)
- Deal with URL processing
- Define HTTP context for data: URLs, about:blank, and file: URLs.
- Progress Events
The basic model is Request -> Fetch -> Response.
- URL (as object)
- UA headers
- author headers (maybe rename because people get upset with "author")
- entity body
- manual redirect flag
- omit credentials flag
- force preflight flag (set for upload progress notifications (to not reveal existence of server in case of POST I suppose; I should know...))
XXX add CORS modes and whatever HTML fetch defines.
Have a case-switch on URL scheme. See also URL. Fetch results in a network error response unless the scheme is one of
CORS stuff is only relevant for http/https. Can be relevant even for same-origin requests in case of cross-origin redirect without the manual redirect flag set.
Both intermediate updates (progress, headers received, ...) and final. Also indicates network error / CORS error (exposed as network error), ...