[
https://issues.apache.org/jira/browse/SLING-152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12558558#action_12558558
]
Alexander Klimetschek commented on SLING-152:
---------------------------------------------
My (hopefully helpful) experiences with this topic can be found here:
http://cocoon.apache.org/2.2/1366_1_1.html
Most notably does Jetty use UTF-8 encoding by default and not ISO-8859-1 as
defined by the servlet engine spec, which is kinda hard to find out. In the end
the only way to do it reliably is to explicitly set UTF-8 encoding everywhere
(ie. in the HTTP content type and meta tag content-type). UTF-8 is assumed to
be the best encoding practically, but it should be configurable for the Sling
admin anyway.
> POST parameters are read from request body even when contentType is
> application/x-www-form-urlencoded
> -----------------------------------------------------------------------------------------------------
>
> Key: SLING-152
> URL: https://issues.apache.org/jira/browse/SLING-152
> Project: Sling
> Issue Type: Bug
> Components: Core
> Reporter: Dominique Pfister
>
> In a POST request with content type application/x-www-form-urlencoded,
> Sling's internal ParameterSupport class (in sling-core) builds a parameter
> map by parsing the request body available via
> ServletRequest.getInputStream(). However, if some other component (e.g. a
> servlet filter) has already looked at some parameter,
> ServletRequest.getInputStream() will return an empty stream, compliant with
> Servlet API Specification 2.4 SRV.4.1.1.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
