node-fetch/LIMITS.md


Known differences
=================

*As of 2.x release*

- Topics such as Cross-Origin, Content Security Policy, Mixed Content, Service Workers are ignored, given our server-side context.

- URL input must be an absolute URL, using either `http` or `https` as scheme.

- On the upside, there are no forbidden headers.

- `res.url` contains the final url when following redirects.

- For convenience, `res.body` is a Node.js [Readable stream][readable-stream], so decoding can be handled independently.

- Similarly, `req.body` can either be `null`, a string, a buffer or a Readable stream.

- Also, you can handle rejected fetch requests through checking `err.type` and `err.code`. See [ERROR-HANDLING.md][] for more info.

- Only support `res.text()`, `res.json()`, `res.blob()`, `res.arraybuffer()`, `res.buffer()`

- There is currently no built-in caching, as server-side caching varies by use-cases.

- Current implementation lacks server-side cookie store, you will need to extract `Set-Cookie` headers manually.

- If you are using `res.clone()` and writing an isomorphic app, note that stream on Node.js have a smaller internal buffer size (16Kb, aka `highWaterMark`) from client-side browsers (>1Mb, not consistent across browsers).

[readable-stream]: https://nodejs.org/api/stream.html#stream_readable_streams
[ERROR-HANDLING.md]: https://github.com/bitinn/node-fetch/blob/master/ERROR-HANDLING.md
basic fetch feature done 2015-01-26 09:46:32 -08:00
update document 2015-05-03 03:07:20 -07:00			`Known differences`
			`=================`
basic fetch feature done 2015-01-26 09:46:32 -08:00
Documentation update for v2 (#214) 2016-12-08 19:18:06 -08:00			`As of 2.x release`
basic fetch feature done 2015-01-26 09:46:32 -08:00
update limit document 2016-09-11 08:08:11 -07:00			`- Topics such as Cross-Origin, Content Security Policy, Mixed Content, Service Workers are ignored, given our server-side context.`
basic fetch feature done 2015-01-26 09:46:32 -08:00
update limit document 2016-09-11 08:08:11 -07:00			- URL input must be an absolute URL, using either `http` or `https` as scheme.
basic fetch feature done 2015-01-26 09:46:32 -08:00
More documentation 2017-02-26 16:52:32 -08:00			`- On the upside, there are no forbidden headers.`
basic fetch feature done 2015-01-26 09:46:32 -08:00
More documentation 2017-02-26 16:52:32 -08:00			- `res.url` contains the final url when following redirects.
basic fetch feature done 2015-01-26 09:46:32 -08:00
More documentation 2017-02-26 16:52:32 -08:00			- For convenience, `res.body` is a Node.js [Readable stream][readable-stream], so decoding can be handled independently.
basic fetch feature done 2015-01-26 09:46:32 -08:00
More documentation 2017-02-26 16:52:32 -08:00			- Similarly, `req.body` can either be `null`, a string, a buffer or a Readable stream.

			- Also, you can handle rejected fetch requests through checking `err.type` and `err.code`. See [ERROR-HANDLING.md][] for more info.
doc update 2016-04-05 10:32:37 -07:00
Documentation update for v2 (#214) 2016-12-08 19:18:06 -08:00			- Only support `res.text()`, `res.json()`, `res.blob()`, `res.arraybuffer()`, `res.buffer()`
doc update 2015-01-27 10:02:27 -08:00
basic refactor done 2015-01-27 05:11:26 -08:00			`- There is currently no built-in caching, as server-side caching varies by use-cases.`
update limit document on cookie headers 2016-09-11 07:13:00 -07:00
update limit document 2016-09-11 08:08:11 -07:00			- Current implementation lacks server-side cookie store, you will need to extract `Set-Cookie` headers manually.

			- If you are using `res.clone()` and writing an isomorphic app, note that stream on Node.js have a smaller internal buffer size (16Kb, aka `highWaterMark`) from client-side browsers (>1Mb, not consistent across browsers).
More documentation 2017-02-26 16:52:32 -08:00
			`[readable-stream]: https://nodejs.org/api/stream.html#stream_readable_streams`
			`[ERROR-HANDLING.md]: https://github.com/bitinn/node-fetch/blob/master/ERROR-HANDLING.md`