[ https://issues.apache.org/jira/browse/SLING-508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12602946#action_12602946 ]
Felix Meschberger commented on SLING-508: ----------------------------------------- > I meant configuring in the osgi console While I am a big fan of configuration, I tend to think that such integration issues should not be solved by configuration... Given that my solution works for 95% (or more) of the cases, which I am sure of, I don't think we need anything more. > As a simplified example, if Sling provides "âêîôûäëïöü" as the reference > value that must be submitted Not sure whether this works. We could of course write a Filter (later) which recognizes forms in HTML responses and injects such a parameter. On response with parameters (POST and GET), the parameter could be analyzed and acted upon. But again, I don't think we need this right now. > 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.