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

Felix Meschberger resolved SLING-1998.
--------------------------------------

    Resolution: Fixed

Updated documentation in http://sling.apache.org/site/request-parameters.html

> Support configuration of the default request parameter encoding
> ---------------------------------------------------------------
>
>                 Key: SLING-1998
>                 URL: https://issues.apache.org/jira/browse/SLING-1998
>             Project: Sling
>          Issue Type: New Feature
>          Components: Engine
>    Affects Versions: Engine 2.2.2
>            Reporter: Felix Meschberger
>            Assignee: Felix Meschberger
>             Fix For: Engine 2.2.4
>
>
> As proposed in http://markmail.org/message/mv6jfc26x43keg6i a new 
> configuration property for the Sling Main Servlet should be introduced to 
> overwrite the default request parameter encoding.
> Currently request parameters are decoded with the encoding provided by the 
> _charset_ request parameter (if set). If the request parameter is not set or 
> does not provide an encoding supported by the platform, the default 
> ISO-8859-1 is applied.
> For applications always only using the same response encoding, e.g. UTF-8, 
> specifiying the _charset_ request parameter is tedious. It would be helpful 
> if the default parameter could be configured to something different than 
> ISO-8859-1.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to