[TAPESTRY-1594] tapestry-upload processes requests with multipart content even if Tapestry doesn't recognize the page

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 5.0.5
• Fix Version/s: 5.0.10
• Component/s: tapestry-core, tapestry-upload
• Assignee: Howard Lewis Ship
• Reporter: Douglas Hauge
• Created: 22/Jun/07 00:44
• Updated: 12/Oct/10 15:09
• Resolved: 01/Feb/08 18:50

Description

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

Issue Links

• is cloned by: TAPESTRY-2770 CLONE -tapestry-upload processes requests with multipart content even if Tapestry doesn't recognize the page