You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Felix Meschberger (JIRA)" <ji...@apache.org> on 2011/02/26 16:32:05 UTC
[jira] Created: (SLING-1998) Support configuration of the default
request parameter encoding
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
[jira] Commented: (SLING-1998) Support configuration of the default
request parameter encoding
Posted by "Felix Meschberger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-1998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13000194#comment-13000194 ]
Felix Meschberger commented on SLING-1998:
------------------------------------------
Added new configuration parameter "sling.default.parameter.encoding" to the Sling Main Servlet configuration in Rev. 1075262.
If this configuration parameter is set to a valid -- that is supported by the platform -- encoding request parameters will be decoded using this decoding by default unless the _charset_ request parameter is set. If the parameter is not set or not set to a supported encoding the default as specified by the Servlet API specification --- ISO-8859-1 --- is used.
> 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
[jira] Resolved: (SLING-1998) Support configuration of the default
request parameter encoding
Posted by "Felix Meschberger (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Closed] (SLING-1998) Support configuration of the default
request parameter encoding
Posted by "Justin Edelson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-1998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Justin Edelson closed SLING-1998.
---------------------------------
> 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