You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Sam Peters (Jira)" <ji...@apache.org> on 2023/09/06 21:17:00 UTC
[jira] [Updated] (WICKET-7071) Problems when calling request.getInputStream() before executing WicketFilter
[ https://issues.apache.org/jira/browse/WICKET-7071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sam Peters updated WICKET-7071:
-------------------------------
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|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|https://github.com/eclipse-ee4j/jersey/issues/4867.]
was:
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|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.]
> Problems when calling request.getInputStream() before executing WicketFilter
> ----------------------------------------------------------------------------
>
> Key: WICKET-7071
> URL: https://issues.apache.org/jira/browse/WICKET-7071
> Project: Wicket
> Issue Type: Bug
> Components: wicket-core
> Affects Versions: 10.0.0-M1, 9.14.0
> Environment: Java 17 or 21-ea; Jetty 11 or Tomcat 10.1.x; Wicket 10.0.0-M1 or 9.3+.
> Reporter: Sam Peters
> Priority: Major
>
> 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|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|https://github.com/eclipse-ee4j/jersey/issues/4867.]
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)