What a transport resolves with. The engine is lenient about the shapes custom
transports naturally return: headers may be a plain object with names in any
case, a Headers instance or a Map; body may be a Buffer, any other
ArrayBuffer view (a Uint8Array from fetch, a DataView), an ArrayBuffer or a
string (read as UTF-8). Anything else — a missing status, no body — is a
JobsucheNetworkError.
The URL that answered, if the transport knows it (fetch's response.url). When it
is on another origin than the request's, the transport followed a redirect itself
and the engine fails the request (JobsucheNetworkError).
What a transport resolves with. The engine is lenient about the shapes custom transports naturally return:
headersmay be a plain object with names in any case, aHeadersinstance or aMap;bodymay be a Buffer, any other ArrayBuffer view (aUint8Arrayfrom fetch, a DataView), an ArrayBuffer or a string (read as UTF-8). Anything else — a missing status, no body — is a JobsucheNetworkError.