Skip to content

Unable to read error message from response header #339

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

Roman-Shchukin
Copy link
Contributor

@Roman-Shchukin Roman-Shchukin commented Sep 13, 2022

Issue description:
Currently error response doesn't contain headers of original error response

Related issue: #331

Fix description:
Headers added to error response

Changes:
In err object added responseHeaders data with headers of original error response

Documentation changes required: No

Added unit tests: Yes

@Roman-Shchukin Roman-Shchukin requested review from a team as code owners September 13, 2022 17:24
Copy link
Contributor

@localconst localconst left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@Roman-Shchukin Roman-Shchukin changed the title Unable to read error message from response header #331 Unable to read error message from response header Sep 14, 2022
@Roman-Shchukin Roman-Shchukin merged commit df510b7 into microsoft:master Oct 6, 2022
ajuanjojjj pushed a commit to ajuanjojjj/typed-rest-client that referenced this pull request Jul 5, 2024
* Added response headers to err answer

* Corrected message in test

* Corrected package version
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants