Bug #1644
Redirects after StopAction exceptions not carried out correctly
| Status: | Resolved | Start date: | 2008-10-03 | |
|---|---|---|---|---|
| Priority: | Must have | Due date: | 2008-10-03 | |
| Assigned To: | Karsten Dambekalns | % Done: | 100% |
|
| Category: | MVC | |||
| Target version: | - | |||
| PHP Version: | Complexity: | |||
| Has patch: | Affected Flow version: |
Description
When calling the backend of the TYPO3 package without a valid login one would get the backend HTML delivered - and after that would be the redirect HTML produced by getPreparedController() in case authentication is required. The request inside that method itself was correct, including 302 status code and location header. But, since the StopAction exception was ignored, the dispatcher got the LoginController next and continued processing the reuqest, overriding the "failure", and bang - here you are.
Associated revisions
FLOW3:
- fixed handling of StopAction exception in MVC dispatcher by marking the request as dispatched when an AuthenticationRequired exception is catched in getPreparedController(); fixes #1644.
History
#1 Updated by Karsten Dambekalns almost 7 years ago
- Status changed from Accepted to Resolved
- % Done changed from 0 to 100
Applied in changeset r1320.