- Enhance: error handling document to explain
FetchErrordesign - Fix: support
form-data2.x releases (requiresform-data>= 2.1.0)
- Enhance: minor document update
- Fix: response.json() returns empty object on 204 no-content response instead of throwing a syntax error
- Fix: if
res.bodyis a non-stream non-formdata object, we will callbody.toStringand send it as a string - Fix:
countervalue is incorrectly set tofollowvalue when wrapping Request instance - Fix: documentation update
- Enhance: added
res.buffer()api for convenience, it returns body as a Node.js buffer - Enhance: better old server support by handling raw deflate response
- Enhance: skip encoding detection for non-HTML/XML response
- Enhance: minor document update
- Fix: HEAD request doesn't need decompression, as body is empty
- Fix:
req.bodynow accepts a Node.js buffer
- Fix: handle 204 and 304 responses when body is empty but content-encoding is gzip/deflate
- Fix: allow resolving response and cloned response in any order
- Fix: avoid setting
content-lengthwhenform-databody use streams - Fix: send DELETE request with content-length when body is present
- Fix: allow any url when calling new Request, but still reject non-http(s) url in fetch
- Fix: allow node.js core to handle keep-alive connection pool when passing a custom agent
- Fix: redirect mode
manualshould work even when there is no redirection or broken redirection
- Enhance: rejected promise now use custom
Error(thx to @pekeler) - Enhance:
FetchErrorcontainserr.typeanderr.code, allows for better error handling (thx to @pekeler) - Enhance: basic support for redirect mode
manualanderror, allows for location header extraction (thx to @jimmywarting for the initial PR)
- Fix: wrapping Request instance with FormData body again should preserve the body as-is
- Enhance: Request and Response now have
clonemethod (thx to @kirill-konshin for the initial PR) - Enhance: Request and Response now have proper string and buffer body support (thx to @kirill-konshin)
- Enhance: Body constructor has been refactored out (thx to @kirill-konshin)
- Enhance: Headers now has
forEachmethod (thx to @tricoder42) - Enhance: back to 100% code coverage
- Fix: better form-data support (thx to @item4)
- Fix: better character encoding detection under chunked encoding (thx to @dsuket for the initial PR)
- Fix: make sure
Content-Lengthheader is set when body is string for POST/PUT/PATCH requests - Fix: handle body stream error, for cases such as incorrect
Content-Encodingheader - Fix: when following certain redirects, use
GETon subsequent request per Fetch Spec - Fix:
RequestandResponseconstructors now parse headers input usingHeaders
- Enhance: allow auto detect of form-data input (no
FormDataspec on node.js, this is form-data specific feature)
- Enhance: allow custom host header to be set (server-side only feature, as it's a forbidden header on client-side)
- Enhance: now
fetch.Requestis exposed as well
- Enhance:
Headersnow normalizedNumbervalue toString, prevent common mistakes
- Enhance: now fetch.Headers and fetch.Response are exposed, making testing easier
- Fix:
Headersshould only supportStringandArrayproperties, and ignore others
- Enhance: now req.headers accept both plain object and
Headersinstance
- Enhance: timeout now also applies to response body (in case of slow response)
- Fix: timeout is now cleared properly when fetch is done/has failed
- Fix: less greedy content-type charset matching
- Fix: when
follow = 0, fetch should not follow redirect - Enhance: update tests for better coverage
- Enhance: code formatting
- Enhance: clean up doc
- Enhance: test iojs support
- Enhance: timeout attached to socket event only fire once per redirect
- Fix: response size limit should reject large chunk
- Enhance: added character encoding detection for xml, such as rss/atom feed (encoding in DTD)
- Fix: added res.ok per spec change
- Enhance: better test coverage and doc
- Major: initial public release