Repository navigation
Conversation
robhudson
force-pushed
the
streaming-nonce
branch
from
October 24, 2026 20:49
0859dcf to
3dca1d4
Compare
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
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.
Streaming responses (
StreamingHttpResponse,FileResponse) could send a CSP header without the nonce, because the body is rendered after the middleware writes the header. The middleware now generates the nonce for streaming responses before writing the header. This ports Django's fix for the same bug (#37419).Streaming responses now always include a nonce in the header. Browsers ignore
'unsafe-inline'when a nonce is present, so policies combiningNONCEandUNSAFE_INLINEin one directive may now block inline styles or scripts. This is documented indocs/nonce.rst.