[WICKET-7071] Problems when calling request.getInputStream() before executing WicketFilter

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Not A Bug
• Affects Version/s: 10.0.0-M1, 9.14.0
• Fix Version/s: 9.15.0, 10.0.0-M2
• Component/s: wicket-core
• Environment: Java 17 or 21-ea; Jetty 11 or Tomcat 10.1.x; Wicket 10.0.0-M1 or 9.3+.
• Assignee: Unassigned
• Reporter: Sam Peters
• Created: 05/Sep/23 14:28
• Updated: 13/Sep/23 19:11
• Resolved: 13/Sep/23 19:11

Description

Calling request.getInputStream() (without reading any data from the stream), followed by a WicketFilter, causes certain wicket requests to fail.

If no call to request.getInputStream() is made, everything works as expected.

See runnable, minimal Maven project here: https://github.com/gluser1357/jerseyissues/tree/issue-4867-wicket10 > readme.txt.

The issue is always reproducable e. g. in Jetty 11 and Tomcat 10.1.x (Jakarta Servlet 5+).

A use case for the described filter combination is e. g. to add an existing Jersey-based authorization filter in front of a Wicket application. Since Jersey calls at some point request.getInputStream(), our Wicket application fails at then. See more details on this here: https://github.com/eclipse-ee4j/jersey/issues/4867