7.0.0

Breaking changes

• Changes stringifying options behavior. 51a3eaf
  Setting the body option to be an object to stringify is no longer possible without setting either the form option for URL encoding or the json option for JSON encoding. Previously, Got would use URL encoding by default, now it will throw an error. Since the json option also means Got will decode a JSON response for you, setting both options to true will encode the request as URL and decode the response as JSON.
• Now also redirects on 307, 308, 303 responses. b45896a
• The timeout option now applies to the whole request and we added ability to control the timeout of the individual phases. 7964f2c

Highlights

• Added ability to cancel in-progress requests! 9ef7a5a
• Added WHATWG URL support. f501fc2
• Improve request retries by reducing the number of retries and making delays shorter. 14d0859
• Only throws ParseError when parsing fails on 2xx responses. c86706b
• No longer throws HTTPError on 304 responses. 7b12b75
• Added protocol property to errors. 919703c
• Added url property to errors. a287f8e
• Includes response headers in errors, and redirect URLs in errors and the response. 8b4d06e
• Improve use in Electron. 2130570 6fc1902

All changes

v6.7.1...v7.0.0

6.7.0

This minor release fixes timeout behaviour to correspond with readme:

Milliseconds to wait for a server to send response headers before aborting request with ETIMEDOUT error.

Before this release ESOCKTIMEDOUT can be thrown (which can lead to false-positive errors for keep-alive sockets).

6.6.0

• Add requestUrl to response in streaming mode (#230)
• new Buffer() => Buffer.from() 5888ca7
• Add url to response (#236)
• timed-out updated to ^3.0.0

5.7.0 – Last minor release of 5.x branch

This is last release of 5.x branch (which compatible with old versions of Node.JS). In this release we pulled all fixes (only UTF in headers is not cherry-picked):

• Add url to response (#236)
• Add requestUrl to response in streaming mode (#230)
• Allow non-plain object as request body (#217)
• Fixed unexpected EOF when decompressing content
• Detect formdata body and set content-type header (#220)
• Add a requestUrl property to the response object (#205)
• Add redirect url to response object (#191)

🎃 Happy Halloween!

6.5.0

• Add a redirect url property to the response object (#191)
• Add a requestUrl property to the response object (#205)
• ⬆️ get-stream bumped to ^2.3.0 – which fixes some nasty encoding bugs
• Fix location encoding (#214)
• Detect formdata body and set content-type header (#220)
• ⬆️ unzip-response bumped to ^2.0.1 – which fixes unexpected EOF error
• Allow non-plain object as request body (#217)

Changes

v6.3.0...v6.5.0

6.3.0

followRedirect option

This option disables following redirects and got will not treat them as errors:

const res = await got(`google.com`, {followRedirect: false});
res.statusCode === 302; // true

By default this option is true, so no major changes in code are needed.

Changes

v6.2.0...v6.3.0

6.2.0

• 26a499c statusCode and statusMessage added to ParseError object

6.1.2

• 45a636c fixes errors on parsing empty JSON body
• f9078b6 fixes default user-agent to be RFS complaint

6.1.1

• f9ef29a fixes redirects with uppercased method option

6.1.0

Non-retrieable errors

In got@5 we introduced retries option, which (as name says) retry request on every Error. For most errors this was right thing to do, but in case ENETUNREACH and ENOTFOUND retries are pointless.

This version removes retries from such errors, so you will get instant error, when typo gets into configs.

Changes

v6.0.0...v6.1.0