Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[Book][Security] Fix typo and remove redundant sentence #4743

Merged
merged 1 commit into from Jan 3, 2015
Merged

[Book][Security] Fix typo and remove redundant sentence #4743

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
5 changes: 2 additions & 3 deletions book/security.rst
View file
Open in desktop
Expand Up @@ -655,7 +655,7 @@ There are **two** ways to deny access to something:
Securing URL patterns (access_control)
......................................

The most basic way to secure part of your application is to secure an entire
The most basic way to secure parts of your application is to secure an entire
URL pattern. You saw this earlier, where anything matching the regular expression
``^/admin`` requires the ``ROLE_ADMIN`` role:

Expand Down Expand Up @@ -1082,8 +1082,7 @@ Next, you'll need to create a route for this URL (but not a controller):
return $collection;

And that's it! By sending a user to ``/logout`` (or whatever you configure
the ``path`` to be), Symfony will un-authenticate the current user. and
redirect them the homepage (the value defined by ``target``).
the ``path`` to be), Symfony will un-authenticate the current user.

Once the user has been logged out, they will be redirected to whatever path
is defined by the ``target`` parameter above (e.g. the ``homepage``).
Expand Down