Skip to content

Commit d74e2c1

Browse files
Ryan Castleweaverryan
Ryan Castle
authored andcommitted
Improved clarity of explanation around overriding setTargetPath()
1 parent c2be78b commit d74e2c1

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

cookbook/security/target_path.rst

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -10,9 +10,9 @@ the name of the firewall, defined in ``security.yml``). Upon a successful
1010
login, the user is redirected to this path, as to help them continue from the
1111
last known page they visited.
1212

13-
On some occasions, this is unexpected. For example when the last request before logout
14-
was an XMLHttpRequest route, the user may be redirected back to an invalid
15-
route.
13+
In some situations, this is not ideal. For example when the last request
14+
URI was an XMLHttpRequest which returned a non-HTML or partial HTML response,
15+
the user is redirected back to a page which the browser cannot render.
1616

1717
To get around this behavior, you would simply need to extend the ``ExceptionListener``
1818
class and override the default method named ``setTargetPath()``.

0 commit comments

Comments
 (0)