About
@adobe/fetch
in general adheres to the Fetch API Specification, implementing a subset of the API. However, there are some notable deviations:
Response.body
returns a Node.js Readable stream.Response.blob()
is not implemented. Use Response.buffer()
instead.Response.formData()
is not implemented.- Cookies are not stored by default. However, cookies can be extracted and passed by manipulating request and response headers.
- The following values of the
fetch()
option cache
are supported: 'default'
(the implicit default) and 'no-store'
. All other values are currently ignored. - The following
fetch()
options are ignored due to the nature of Node.js and since @adobe/fetch
doesn't have the concept of web pages: mode
, referrer
, referrerPolicy
, integrity
and credentials
. - The
fetch()
option keepalive
is not supported. But you can use the h1.keepAlive
context option, as demonstrated here.
@adobe/fetch
also supports the following non-spec extensions:
Response.buffer()
returns a Node.js Buffer
.Response.url
contains the final url when following redirects.- The
body
that can be sent in a Request
can also be a Readable
Node.js stream, a Buffer
, a string or a plain object. - There are no forbidden header names.
- The
Response
object has an extra property httpVersion
which is one of '1.0'
, '1.1'
or '2.0'
, depending on what was negotiated with the server. - The
Response
object has an extra property fromCache
which determines whether the response was retrieved from cache. - The
Response
object has an extra property decoded
which determines whether the response body was automatically decoded (see Fetch option decode
below). Response.headers.plain()
returns the headers as a plain object.Response.headers.raw()
returns the internal/raw representation of the headers where e.g. the Set-Cokkie
header is represented with an array of strings value.- The Fetch option
follow
allows to limit the number of redirects to follow (default: 20
). - The Fetch option
compress
enables transparent gzip/deflate/br content encoding (default: true
). - The Fetch option
decode
enables transparent gzip/deflate/br content decoding (default: true
).
Note that non-standard Fetch options have been aligned with node-fetch where appropriate.
Features
Installation
Note:
As of v2 Node version >= 12 is required.
$ npm install @adobe/fetch
API
Apart from the standard Fetch API
fetch()
Request
Response
Headers
Body
@adobe/fetch
exposes the following non-spec extensions:
context()
- creates a new customized API contextreset()
- resets the current API context, i.e. closes pending sessions/sockets, clears internal caches, etc ...onPush()
- registers an HTTP/2 Server Push listeneroffPush()
- deregisters a listener previously registered with onPush()
clearCache()
- clears the HTTP cache (cached responses)cacheStats()
- returns cache statisticsnoCache()
- creates a customized API context with disabled caching (convenience)h1()
- creates a customized API context with enforced HTTP/1.1 protocol (convenience)keepAlive()
- creates a customized API context with enforced HTTP/1.1 protocol and persistent connections (convenience)h1NoCache()
- creates a customized API context with disabled caching and enforced HTTP/1.1 protocol (convenience)keepAliveNoCache()
- creates a customized API context with disabled caching and enforced HTTP/1.1 protocol with persistent connections (convenience)createUrl()
- creates a URL with query parameters (convenience)timeoutSignal()
- ceates a timeout signal (convenience)
Context
An API context allows to customize certain aspects of the implementation and provides isolation of internal structures (session caches, HTTP cache, etc.) per API context.
The following options are supported:
interface ContextOptions {
userAgent?: string;
maxCacheSize?: number;
alpnProtocols?: ReadonlyArray< ALPNProtocol >;
alpnCacheTTL?: number;
rejectUnauthorized?: boolean;
alpnCacheSize?: number;
h1?: Http1Options;
h2?: Http2Options;
};
interface Http1Options {
keepAlive?: boolean;
keepAliveMsecs?: number;
rejectUnauthorized?: boolean;
maxCachedSessions?: number;
}
interface Http2Options {
idleSessionTimeout?: number;
enablePush?: boolean;
pushedStreamIdleTimeout?: number;
rejectUnauthorized?: boolean;
};
Common Usage Examples
Access Response Headers and other Meta data
const { fetch } = require('@adobe/fetch');
const resp = await fetch('https://httpbin.org/get');
console.log(resp.ok);
console.log(resp.status);
console.log(resp.statusText);
console.log(resp.httpVersion);
console.log(resp.headers.plain());
console.log(resp.headers.get('content-type'));
Fetch JSON
const { fetch } = require('@adobe/fetch');
const resp = await fetch('https://httpbin.org/json');
const jsonData = await resp.json();
Fetch text data
const { fetch } = require('@adobe/fetch');
const resp = await fetch('https://httpbin.org/');
const textData = await resp.text();
Fetch binary data
const { fetch } = require('@adobe/fetch');
const resp = await fetch('https://httpbin.org//stream-bytes/65535');
const imageData = await resp.buffer();
Specify a timeout for a fetch
operation
Using timeoutSignal(ms)
non-spec extension:
const { fetch, timeoutSignal, AbortError } = require('@adobe/fetch');
const signal = timeoutSignal(1000);
try {
const resp = await fetch('https://httpbin.org/json', { signal });
const jsonData = await resp.json();
} catch (err) {
if (err instanceof AbortError) {
console.log('fetch timed out after 1s');
}
} finally {
signal.clear();
}
Using AbortController
:
const { fetch, AbortController, AbortError } = require('@adobe/fetch');
const controller = new AbortController();
const timerId = setTimeout(() => controller.abort(), 1000);
const { signal } = controller;
try {
const resp = await fetch('https://httpbin.org/json', { signal });
const jsonData = await resp.json();
} catch (err) {
if (err instanceof AbortError) {
console.log('fetch timed out after 1s');
}
} finally {
clearTimeout(timerId);
}
Stream an image
const fs = require('fs');
const { fetch } = require('@adobe/fetch');
const resp = await fetch('https://httpbin.org/image/jpeg');
resp.body.pipe(fs.createWriteStream('saved-image.jpg'));
Post JSON
const { fetch } = require('@adobe/fetch');
const method = 'POST';
const body = { foo: 'bar' };
const resp = await fetch('https://httpbin.org/post', { method, body });
Post JPEG image
const fs = require('fs');
const { fetch } = require('@adobe/fetch');
const method = 'POST';
const body = fs.createReadStream('some-image.jpg');
const headers = { 'content-type': 'image/jpeg' };
const resp = await fetch('https://httpbin.org/post', { method, body, headers });
Post form data
const { FormData, Blob, File } = require('formdata-node');
const { fileFromPath } = require('formdata-node/file-from-path');
const { fetch } = require('@adobe/fetch');
const method = 'POST';
const fd = new FormData();
fd.set('field1', 'foo');
fd.set('field2', 'bar');
fd.set('blob', new Blob([0x68, 0x65, 0x6c, 0x69, 0x78, 0x2d, 0x66, 0x65, 0x74, 0x63, 0x68]));
fd.set('file', new File(['File content goes here'], 'file.txt'));
fd.set('other_file', await fileFromPath('/foo/bar.jpg', 'bar.jpg', { type: 'image/jpeg' }));
const resp = await fetch('https://httpbin.org/post', { method, body: fd });
GET with query parameters object
const { createUrl, fetch } = require('@adobe/fetch');
const qs = {
fake: 'dummy',
foo: 'bar',
rumple: "stiltskin",
};
const resp = await fetch(createUrl('https://httpbin.org/json', qs));
or using URLSearchParams
:
const { fetch } = require('@adobe/fetch');
const body = new URLSearchParams({
fake: 'dummy',
foo: 'bar',
rumple: "stiltskin",
});
const resp = await fetch('https://httpbin.org/json', { body });
Cache
Responses of GET
and HEAD
requests are by default cached, according to the rules of RFC 7234:
const { fetch } = require('@adobe/fetch');
const url = 'https://httpbin.org/cache/60';
let resp = await fetch(url);
assert(resp.ok);
assert(!resp.fromCache);
resp = await fetch(url);
assert(resp.ok);
assert(resp.fromCache);
You can disable caching per request with the cache: 'no-store'
option:
const { fetch } = require('@adobe/fetch');
const resp = await fetch('https://httbin.org/', { cache: 'no-store' });
assert(resp.ok);
assert(!resp.fromCache);
You can disable caching entirely:
const { fetch } = require('@adobe/fetch').noCache();
Advanced Usage Examples
HTTP/2 Server Push
Note that pushed resources will be automatically and transparently added to the cache.
You can however add a listener which will be notified on every pushed (and cached) resource.
const { fetch, onPush } = require('@adobe/fetch');
onPush((url, response) => console.log(`received server push: ${url} status ${response.status}`));
const resp = await fetch('https://nghttp2.org');
console.log(`Http version: ${resp.httpVersion}`);
Force HTTP/1(.1) protocol
const { fetch } = require('@adobe/fetch').h1();
const resp = await fetch('https://nghttp2.org');
console.log(`Http version: ${resp.httpVersion}`);
HTTP/1.1 Keep-Alive
const { fetch } = require('@adobe/fetch').keepAlive();
const resp = await fetch('https://httpbin.org/status/200');
console.log(`Connection: ${resp.headers.get('connection')}`);
Unlike browsers, you can access raw Set-Cookie
headers manually using Headers.raw()
. This is an @adobe/fetch
only API.
const { fetch } = require('@adobe/fetch');
const resp = await fetch('https://httpbin.org/cookies/set?a=1&b=2');
console.log(resp.headers.raw()['set-cookie']);
Self-signed Certificates
const { fetch } = require('@adobe/fetch').context({ rejectUnauthorized: false });
const resp = await fetch('https://localhost:8443/');
Set cache size limit
const { fetch, cacheStats } = require('@adobe/fetch').context({
maxCacheSize: 100 * 1024,
});
let resp = await fetch('https://httpbin.org/bytes/60000');
resp = await fetch('https://httpbin.org/bytes/50000');
console.log(cacheStats());
Disable caching
const { fetch } = require('@adobe/fetch').noCache();
let resp = await fetch('https://httpbin.org/cache/60');
resp = await fetch('https://httpbin.org/cache/60');
assert(!resp.fromCache);
Set a custom user agent
const { fetch } = require('@adobe/fetch').context({
userAgent: 'custom-fetch'
});
const resp = await fetch('https://httpbin.org//user-agent');
const json = await resp.json();
console.log(json['user-agent']);
More examples
More example code can be found in the test source files.
Development
Build
$ npm install
Test
$ npm test
Lint
$ npm run lint
Troubleshooting
You can enable @adobe/fetch
low-level debug console output by setting the DEBUG
environment variable to adobe/fetch*
, e.g.:
$ DEBUG=adobe/fetch* node test.js
This will produce console outout similar to:
...
adobe/fetch:core established TLS connection:
adobe/fetch:core www.nghttp2.org -> h2 +0ms
adobe/fetch:h2 reusing socket
adobe/fetch:h2 GET www.nghttp2.org/httpbin/user-agent +0ms
adobe/fetch:h2 session https://www.nghttp2.org established +1ms
adobe/fetch:h2 caching session https://www.nghttp2.org +0ms
adobe/fetch:h2 session https://www.nghttp2.org remoteSettings: {"headerTableSize":8192,"enablePush":true,"initialWindowSize":1048576,"maxFrameSize":16384,"maxConcurrentStreams":100,"maxHeaderListSize":4294967295,"maxHeaderSize":4294967295,"enableConnectProtocol":true} +263ms
adobe/fetch:h2 session https://www.nghttp2.org localSettings: {"headerTableSize":4096,"enablePush":true,"initialWindowSize":65535,"maxFrameSize":16384,"maxConcurrentStreams":4294967295,"maxHeaderListSize":4294967295,"maxHeaderSize":4294967295,"enableConnectProtocol":false} +0ms
adobe/fetch:h2 session https://www.nghttp2.org closed +6ms
adobe/fetch:h2 discarding cached session https://www.nghttp2.org +0ms
...
Additionally, you can enable Node.js low-level debug console output by setting the NODE_DEBUG
environment variable appropriately, e.g.
$ export NODE_DEBUG=http*,stream*
$ export DEBUG=adobe/fetch*
$ node test.js
Note: this will flood the console with highly verbose debug output.
Acknowledgement
Thanks to node-fetch and github/fetch for providing a solid implementation reference.
License
Apache 2.0