[
https://issues.apache.org/jira/browse/SLING-508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12602939#action_12602939
]
Bertrand Delacretaz commented on SLING-508:
-------------------------------------------
One thing that might help (though I'm not sure if it fits people's use cases)
is for Sling to provide a value that can be added as a hidden parameter in
forms, and allows the encoding to be recognized when processing the parameters.
As a simplified example, if Sling provides "âêîôûäëïöü" as the reference value
that must be submitted with a predefined parameter name, we could check that
this value decodes correctly with a few possible encodings, to select the
encoding to use for the other parameters.
Not an ideal solution, but that should work. Maybe in addition (optional,
provided by a separate bundle) to what Felix suggests.
> Parameter decoding uses wrong default charset
> ---------------------------------------------
>
> Key: SLING-508
> URL: https://issues.apache.org/jira/browse/SLING-508
> Project: Sling
> Issue Type: Bug
> Components: Engine
> Affects Versions: 2.0.0
> Reporter: Tobias Bocanegra
> Assignee: Felix Meschberger
> Priority: Blocker
>
> As of SLING-152 the request paremeters are re-encoded if a _charset_
> parameter is present. it assumes that the default encoding is
> UTF-8 which is not the case for servlet spec compliant containers (eg.
> tomcat).
> change the default encoding to ISO-8851-1 or make it configurable.
> see:
> http://svn.apache.org/viewvc/incubator/sling/trunk/engine/src/main/java/org/apache/sling/engine/impl/parameters/Util.java?view=markup
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
