-
Notifications
You must be signed in to change notification settings - Fork 26.2k
fix(http): Include HTTP status code and headers when HTTP requests errored in httpResource
#60802
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
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It looks like it broke some tests, can you have a look at it. Thank you.
c21e07f
to
9a46c98
Compare
Yeah, just saw it, I tried to run them on my computer, but there were a lot of errors that were related to not being able to run the chrome sandboxes that crashed with SEGFAULTs. |
You should be able to run the node only test with |
…rored in `httpResource` Currently the HTTP status code and headers are only included if the request succeeded. Given status codes convey more information in case of a request error vs. success, this makes it more useful than inspecting what is contained in `.error()`.
9a46c98
to
424ea34
Compare
Ah thanks, that is faster as well :') I ran it on I just fixed the tests. |
This PR was merged into the repository by commit 9f31947. The changes were merged into the following branches: main, 19.2.x |
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Currently the HTTP status code and headers are only included if the request succeeded. Given status codes convey more information in case of a request error vs. success, this makes it more useful than inspecting what is contained in
.error()
.PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
Issue Number: N/A
What is the new behavior?
Does this PR introduce a breaking change?
Other information
I'm not sure if the current behaviour is actually intended, but I don't really see why statusCode would exist if it was not meant to contain something else than 200 (or 204, but you get my point).