Skip to content

Fixing variable name for target_path #2345

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

Merged
merged 1 commit into from
Mar 30, 2013
Merged

Fixing variable name for target_path #2345

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.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 5 additions & 4 deletions cookbook/security/target_path.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,9 +5,10 @@ How to change the Default Target Path Behavior
==============================================

By default, the security component retains the information of the last request
URI in a session variable named ``_security.target_path``. Upon a successful
login, the user is redirected to this path, as to help her continue from
the last known page she visited.
URI in a session variable named ``_security.main.target_path`` (with ``main`` being
the name of the firewall area, defined in the ``security.yml``). Upon a successful
login, the user is redirected to this path, as to help her continue from the last
known page she visited.

On some occasions, this is unexpected. For example when the last request
URI was an HTTP POST against a route which is configured to allow only a POST
Expand Down Expand Up @@ -61,7 +62,7 @@ Next, create your own ``ExceptionListener``::
return;
}

$request->getSession()->set('_security.target_path', $request->getUri());
$request->getSession()->set('_security.main.target_path', $request->getUri());
}
}

Expand Down