Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

Commit 7a7a842

Browse filesBrowse files
javiereguiluzxabbuh
authored andcommitted
Explained the edge-case where the use_referer option doesn't work
1 parent 7a58612 commit 7a7a842
Copy full SHA for 7a7a842

File tree

Expand file treeCollapse file tree

1 file changed

+8
-1
lines changed
Filter options
Expand file treeCollapse file tree

1 file changed

+8
-1
lines changed

‎reference/configuration/security.rst

Copy file name to clipboardExpand all lines: reference/configuration/security.rst
+8-1Lines changed: 8 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -348,7 +348,14 @@ use_referer
348348
**type**: ``boolean`` **default**: ``false``
349349

350350
If ``true``, the user is redirected to the value stored in the ``HTTP_REFERER``
351-
header when no previous URL was stored in the session.
351+
header when no previous URL was stored in the session. If the referrer URL is
352+
the same as the one generated with the ``login_path`` route, the user is
353+
redirected to the ``default_target_path`` to avoid a redirection loop.
354+
355+
.. note::
356+
357+
For historical reasons, and to match the misspelling of the HTTP standard,
358+
the option is called ``use_referer`` instead of ``use_referrer``.
352359

353360
.. _reference-security-pbkdf2:
354361

0 commit comments

Comments
0 (0)
Morty Proxy This is a proxified and sanitized view of the page, visit original site.