rewrite_response hook: (HTTP status) code
updates should sometimes automatically update reason
#304
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I noticed an annoying discrepancy between Tornado's
HTTPResponse
and myRewritableResponse
when changing the HTTP code. In Tornado, the.reason
attribute defaults to the text corresponding to the.code
attribute. However, inRewritableResponse
, we expect the.code
attribute to be changed. If you change.code
, then.reason
retains the text generated for the previous code. In this PR, I add an observer which updates the.reason
attribute if.code
has changed and.reason
still has its default value.I also extended the documentation to illustrate more of the functionality provided, and extended the tests accordingly.