Skip to content

Conversation

@AdamWill
Copy link
Contributor

In werkzeug 2.0.0 and later, the Location header autocorrection
moved from BaseResponse to Response, so we need to set
autocorrect_location_header = False in Response not
BaseResponse. For now let's just set it in both to be safe,
this doesn't cause any errors at least with 1.0.1 and 2.0.1.

Signed-off-by: Adam Williamson awilliam@redhat.com

…labs#647)

In werkzeug 2.0.0 and later, the Location header autocorrection
moved from BaseResponse to Response, so we need to set
`autocorrect_location_header = False` in `Response` not
`BaseResponse`. For now let's just set it in both to be safe,
this doesn't cause any errors at least with 1.0.1 and 2.0.1.

Signed-off-by: Adam Williamson <awilliam@redhat.com>
@AdamWill AdamWill force-pushed the fix-werkzeug2-autocorrect branch from c5f411d to ccd417e Compare July 19, 2021 22:56
@AdamWill
Copy link
Contributor Author

Fixes #647

@MikeRalphson MikeRalphson self-assigned this Aug 27, 2021
@MikeRalphson MikeRalphson requested a review from kinlane August 27, 2021 12:47
@MikeRalphson
Copy link

@kinlane This PR is a pre-requisite for getting the tests running again when we move them to GitHub Actions - see https://github.com/MikeRalphson/httpbin/actions/runs/1174257560

@AdamWill
Copy link
Contributor Author

Closing in favor of #674 , as setting both isn't valid any more (plus this wasn't doing it entirely right).

@AdamWill AdamWill closed this Sep 14, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants