[
https://issues.apache.org/jira/browse/SLING-152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger resolved SLING-152.
-------------------------------------
Resolution: Fixed
Removing the parsing of all parameters provided by the servlet container. This
not only comprises the url encoded input
stream data but also the query parameters from the request line. We just take
what we get from the servlet container, apply our encoding (if any).
We still keep the parsing of multipart/form-data POST request data, as this is
never handled by the servlet container according to the Servlet API spec.
Fixed in Rev. 613180.
Please close this issue, if this fixes your problems. Thanks.
> 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
> Assignee: Felix Meschberger
>
> 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.
