You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Howard M. Lewis Ship (JIRA)" <de...@tapestry.apache.org> on 2008/01/26 00:04:38 UTC
[jira] Commented: (TAPESTRY-1594) tapestry-upload processes
requests with multipart content even if Tapestry doesn't recognize the page
[ https://issues.apache.org/jira/browse/TAPESTRY-1594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12562743#action_12562743 ]
Howard M. Lewis Ship commented on TAPESTRY-1594:
------------------------------------------------
This is tricky to fix, because the code that decides whether the request is for Tapestry or not has to read query parameters and will have set the encoding.
There's logic that allows Tapestry to rejects requests based on the path, but that code executes after the logic related to multipart content. Perhaps something needs to be done so that such queries can be handled earlier, even if it means coding against the servlet API rather than the Tapestry API.
> tapestry-upload processes requests with multipart content even if Tapestry doesn't recognize the page
> -----------------------------------------------------------------------------------------------------
>
> Key: TAPESTRY-1594
> URL: https://issues.apache.org/jira/browse/TAPESTRY-1594
> Project: Tapestry
> Issue Type: Bug
> Components: tapestry-core, tapestry-upload
> Affects Versions: 5.0.5
> Reporter: Douglas Hauge
>
> We are running Tapestry in a hybrid environment, where some pages are handled by Tapestry and the rest are handled by a legacy servlet. We are using the new Upload component, and are running into a problem where requests with multipart content are processed by services installed by the Upload component even if the page is not a Tapestry page, which interferes with the processing of multipart content on our pages. What seems to happen is
> 1) A request with multipart content is received
> 2) Control is passed to the Tapestry Filter
> 3) Before determining whether the request is for a tapestry page, the MultipartServletRequestFilter process the request
> 4) The Tapestry Filter decides it does not recognize the page, and passes the request on to our servlet
> 5) Our servlet tries to process the multipart request, but fails because the request stream has already been read
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org