Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

11.0.0 Release Notes #162

geek opened this issue Mar 21, 2017 · 0 comments

11.0.0 Release Notes #162

geek opened this issue Mar 21, 2017 · 0 comments


Copy link

@geek geek commented Mar 21, 2017


Version 11.0.0 contains several minor breaking changes that are meant to fix issues and make Wreck more pleasant to work with. As always, the changes are all attached to the appropriate milestone. Of these issues, the notable changes are a simpler response event signature, Boom error objects are now returned when getting a response that has an error status code, and the redirection for 301 and 302 status codes no longer converts the HTTP method to a GET.

Breaking Changes

  1. 301 and 302 redirects no longer convert the HTTP method to GET. Instead, the original HTTP method is used in the redirect request. Since redirects are disabled by default, there is a definite opt-in behavior from the side of the user, therefore this change is appropriate and closely adheres to the guidance of RFC 2616 and RFC 7231. That being said, the assumption that wreck makes is that when you opt-in to redirects that you have confirmed that you do indeed want to follow redirects.

  2. 400 and 500 status codes are converted to boom objects. This means that when upgrading to v11.0.0 of wreck you may encounter error objects returned from requests that previously didn't generate error objects. To determine if the error object is a boom error object, you can check the isBoom property on it.

  3. The response event signature has changed to (err, details). All of the previous arguments after error are now contained as properties on the second argument.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
1 participant
You can’t perform that action at this time.