Movatterモバイル変換


[0]ホーム

URL:


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

Sign up
Appearance settings

Commitcc40b5c

Browse files
committed
Adding missing words thanks to javiereguiluz
1 parent1c568e1 commitcc40b5c

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

‎cookbook/cache/form_csrf_caching.rst‎

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -16,9 +16,9 @@ Why Caching Pages with a CSRF token are Problematic
1616
Typically, each user is assigned a unique CSRF token, which is stored in
1717
the session for validation. This means that if you *do* cache a page with
1818
a form containing a CSRF token, you'll cache the CSRF token of the *first*
19-
user only. When a user submits, the token won't match the token stored in
20-
the session and all users (except for the first) will fail CSRF validation
21-
when submitting the form.
19+
user only. When a user submits the form, the token won't match the token
20+
stored inthe session and all users (except for the first) will fail CSRF
21+
validationwhen submitting the form.
2222

2323
In fact, many reverse proxies (like Varnish) will refuse to cache a page
2424
with a CSRF token. This is because a cookie is sent in order to preserve

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp