[24.2] Fix WSGI response status handling in controller methods #19520
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Fixes galaxyproject#19519. If a string is being set and can't just be the status code cast to a string (which would be correct for ASGI), as that fails in a2wsgi. Easiest and most consistent is to just set the status code to an int and have the wsgi_status method look up the correct description.
github-actions
bot
changed the title
dannon
approved these changes
Feb 4, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Fixes #19519. If a string is being set it can't just be the status code cast to a string (which would be correct for ASGI), as that fails in a2wsgi.
Easiest and most consistent is to just set the status code to an int and have the wsgi_status method look up the correct description.
How to test the changes?
(Select all options that apply)
License