Details
-
Improvement
-
Resolution: Done
-
Neutral
-
None
-
None
-
None
-
None
Description
Currently only mentioned in Upgrading to 6.2 page, but is very much valid for first-time deployments as well.
Possible places:
Symptom:
HTTP Status 400 - Bad Request
Message Invalid character found in the request target [/.rest/delivery/tours/v1/magnolia-travels/Vietnam--Tradition-and-Today?mgnl:created[in]=2015-12-01~2015-12-31]. The valid characters are defined in RFC 7230 and RFC 3986
Description The server cannot or will not process the request due to something that is perceived to be a client error (e.g., malformed request syntax, invalid request message framing, or deceptive request routing).
Exception
java.lang.IllegalArgumentException ...
Checklists
Attachments
Issue Links
- relates to
-
MGNLTOMCAT-6 Tomcat 9 less tolerant on special characters (compared to Tomcat 8)
-
- Closed
-
-
MGNLREST-305 Brackets In Filtered Rest Calls Do Not Work
-
- Closed
-