Skip to content

feat(protocol-http): add reason to HttpResponse #4772

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

Merged
merged 1 commit into from
Jun 6, 2023

Conversation

milesziemer
Copy link
Contributor

Issue

Issue number, if available, prefixed with "#"

N/A

Description

What does this implement/fix? Explain your changes.

Adds reason property to HttpResponse, which is a simple message explaining the status code. The property is optional, so adding it is backward compatible. Http handlers were updated to populate this property when constructing the HttpResponse, except for the Node http2 handler, because http2 doesn't support an equivalent.

Tests were added to Http handlers to make sure the property is populated when available.

Testing

How was this change tested?

Unit tests, CI, and yarn test:integration:legacy

Additional context

Add any other context about the PR here.


By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Adds `reason` property to HttpResponse, which is a simple message
explaining the status code. The property is optional, so adding it
is backward compatible. Http handlers were updated to populate this
property when constructing the HttpResponse, except for the Node http2
handler, because http2 doesn't support an equivalent.

Tests were added to Http handlers to make sure the property is populated
when available.
@milesziemer milesziemer requested review from a team as code owners May 31, 2023 16:22
@milesziemer milesziemer merged commit d29cb58 into aws:main Jun 6, 2023
@github-actions
Copy link

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs and link to relevant comments in this thread.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jun 21, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants