Fix duplicate Date headers in Flask WSGI responses#64726
Open
abhijeets25012-tech wants to merge 1 commit intoapache:mainfrom
Open
Fix duplicate Date headers in Flask WSGI responses#64726abhijeets25012-tech wants to merge 1 commit intoapache:mainfrom
abhijeets25012-tech wants to merge 1 commit intoapache:mainfrom
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
What this PR does
This PR fixes an issue where duplicate
Dateheaders appear in API responses when using Flask alongside Uvicorn.Uvicorn already sets the
Dateheader, and Flask adds another one during response processing, resulting in duplicate headers.How this is fixed
An
after_requesthook is added to the Flask app to remove any existingDateheaders before returning the response.Why this approach
Scope
Testing
Dateheaders