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

Commitc1e5ceb

Browse files
committed
[#1604] Fixing several errors thanks to@stof
1 parentd0aa4ce commitc1e5ceb

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

‎components/security/firewall.rst

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -116,15 +116,15 @@ Flow: Firewall, Authentication, Authorization
116116
Hopefully you can now see a little bit about how the "flow" of the security
117117
context works:
118118

119-
#. the Firewall is registered as a listener on thereques;
119+
#. the Firewall is registered as a listener on the``kernel.request`` event;
120120
#. at the beginning of the request, the Firewall checks the firewall map
121121
to see if any firewall should be active for this URL;
122-
#. If a firewall is foundon the map for this URL, its listeners are notified
122+
#. If a firewall is foundin the map for this URL, its listeners are notified
123123
#. each listener checks to see if the current request contains any authentication
124124
information - a listener may (a) authenticate a user, (b) throw an
125125
``AuthenticationException``, or (c) do nothing (because there is no
126126
authentication information on the request);
127-
#. Once a user isauthentication, you'll use:doc:`/components/security/authorization`
127+
#. Once a user isauthenticated, you'll use:doc:`/components/security/authorization`
128128
to deny access to certain resources.
129129

130130
Read the next sections to find out more about:doc:`/components/security/authentication`

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp