[MAGNOLIA-6952] CMS should handle 400 HTTP-Error internally Created: 07/Feb/17  Updated: 19/Jul/21

Status: Open
Project: Magnolia
Component/s: core
Affects Version/s: 5.3.7, 5.7, 6.2
Fix Version/s: None

Type: New Feature Priority: Neutral
Reporter: zzz_Philipp Güttler Assignee: Unassigned
Resolution: Unresolved Votes: 2
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
causality
relation
Template:
Acceptance criteria:
Empty
Date of First Response:

 Description   

With MAGNOLIA-6025 the handling of encoding-issues in parameter and selector values was modified. Before the patch, magnolia responded with a HTTP 500 Error-Code, after the patch with a HTTP 400.

Unfortunately, this error can not be handled internally, for example by responding with a page from website. In web.xml you can only set an external ressource.

<error-page>
	<error-code>400</error-code>
	<location>/errors/bad-request.html</location>
</error-page>

This behavior differs from the handling of HTTP 404 and should be adapted.



 Comments   
Comment by Ervin Vystup [ 19/Jul/21 ]

Update of the score: 2+(2+2+1)+3+5+5+0=20

Added +1 because of NCS (HELPDESK-1728) and because the maximum is 5. 

Generated at Mon Feb 12 04:19:22 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.