[
https://issues.apache.org/jira/browse/SLING-152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12558560#action_12558560
]
Dominique Pfister commented on SLING-152:
-----------------------------------------
Thanks for the clarification. It is probably safe to assume that a compliant
servlet container will exactly do that, looking at SRV.4.9:
The default encoding of a request the container uses to create the request
reader and parse POST data must be "ISO-8859-1" if none has been specified by
the client request.
> 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.
