Bug #24972

Improve error handling in ExtDirect router

Added by Helmut Hummel over 10 years ago. Updated over 10 years ago.

Status:
Closed
Priority:
Should have
Category:
-
Target version:
Start date:
2011-02-06
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
PHP Version:
Tags:
Complexity:
Is Regression:
Sprint Focus:

Description

Problem:
Even if something goes wrong in a ExtDirect request, the request gets processed, which lead to unexpected results.

Solution:
Do not process the request, but just return the error message instead.

Note:
The current behavior is especially annoying after the addition of the CSRF protection, because in case of an invalid request, a security token error message is sent, which is wrong.

(issue imported from #M17500)


Files

17500.diff (2.86 KB) 17500.diff Administrator Admin, 2011-02-06 18:38
#1

Updated by Steffen Kamper over 10 years ago

committed to 4_5 and trunk rev 10405-10408

Also available in: Atom PDF