[jira] [Closed] (SLING-3409) URL form encoded request parsing fails if charset is set on Content-Type header

["Felix Meschberger (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SLING-3409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Felix Meschberger closed SLING-3409.
------------------------------------


Close after release

> URL form encoded request parsing fails if charset is set on Content-Type header
> -------------------------------------------------------------------------------
>
>                 Key: SLING-3409
>                 URL: https://issues.apache.org/jira/browse/SLING-3409
>             Project: Sling
>          Issue Type: Bug
>          Components: Engine
>            Reporter: Felix Meschberger
>            Assignee: Felix Meschberger
>             Fix For: Engine 2.3.0
>
>
> With SLING-3403 the Engine implements its own request parmeter parsing of query strings and URL encoded form POSTs. URL encoded form posts are recognized by the "application/x-www-form-urlencoded" content type.
> If the charset parameter is set on the content type, such as:
>      application/x-www-form-urlencoded; charset=UTF-8
> the check fails.
> The check should be modified to properly check and ignore the charset parameter.



--
This message was sent by Atlassian JIRA
(v6.2#6252)