From be8d1b628533ac38d2771356e92ade1d61d3f059 Mon Sep 17 00:00:00 2001 From: vishwa Date: Mon, 1 Jun 2026 11:37:03 -0400 Subject: [PATCH] Fixed #37119 -- Clarified middleware ordering note for nonce access. --- docs/ref/middleware.txt | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/ref/middleware.txt b/docs/ref/middleware.txt index e262193699a2..42e7b1b3da2e 100644 --- a/docs/ref/middleware.txt +++ b/docs/ref/middleware.txt @@ -714,9 +714,9 @@ Here are some hints about the ordering of various Django middleware classes: #. :class:`~django.middleware.csp.ContentSecurityPolicyMiddleware` - Can be placed near the bottom, but ensure any middleware that accesses - :ref:`csp_nonce ` is positioned after it, so the nonce is - properly included in the response header. + Can be placed near the bottom, but since the :ref:`csp_nonce ` is + lazy, ensure any middleware that accesses it is positioned after, so the + nonce is generated before this middleware builds the response header. #. :class:`~django.contrib.flatpages.middleware.FlatpageFallbackMiddleware`