You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Felix Meschberger (JIRA)" <ji...@apache.org> on 2010/01/21 09:32:55 UTC
[jira] Created: (FELIX-1999) The classes in the http.base bundle do
not properly handle ServletRequest.getPathInfo() == null
The classes in the http.base bundle do not properly handle ServletRequest.getPathInfo() == null
-----------------------------------------------------------------------------------------------
Key: FELIX-1999
URL: https://issues.apache.org/jira/browse/FELIX-1999
Project: Felix
Issue Type: Bug
Affects Versions: http-2.0.4
Reporter: Felix Meschberger
Assignee: Felix Meschberger
Fix For: http-2.0.6
ServletRequest.getPathInfo() is allowed to return null (if there is no additional path information).
For example, IBM WebSphere returns null if the client accesses the Servlet context without a trailing slash (Jetty in this case redirects to the context path with a trailing slash and thus this case does not happen).
To prevent NullPointerExceptions from happening the FilterHandler.match and ServletHandler.match methods must guard against the uri parameter being null
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (FELIX-1999) The classes in the http.base bundle
do not properly handle ServletRequest.getPathInfo() == null
Posted by "Felix Meschberger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-1999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Felix Meschberger resolved FELIX-1999.
--------------------------------------
Resolution: Invalid
I think this can be closed.
> The classes in the http.base bundle do not properly handle ServletRequest.getPathInfo() == null
> -----------------------------------------------------------------------------------------------
>
> Key: FELIX-1999
> URL: https://issues.apache.org/jira/browse/FELIX-1999
> Project: Felix
> Issue Type: Bug
> Affects Versions: http-2.0.4
> Reporter: Felix Meschberger
> Assignee: Felix Meschberger
> Fix For: http-2.0.6
>
>
> ServletRequest.getPathInfo() is allowed to return null (if there is no additional path information).
> For example, IBM WebSphere returns null if the client accesses the Servlet context without a trailing slash (Jetty in this case redirects to the context path with a trailing slash and thus this case does not happen).
> To prevent NullPointerExceptions from happening the FilterHandler.match and ServletHandler.match methods must guard against the uri parameter being null
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (FELIX-1999) The classes in the http.base bundle
do not properly handle ServletRequest.getPathInfo() == null
Posted by "Felix Meschberger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-1999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12803232#action_12803232 ]
Felix Meschberger commented on FELIX-1999:
------------------------------------------
Fixed said match methods to handle a null uri parameter as if it would be "/" in Rev. 901600. Also added test cases to verify.
> The classes in the http.base bundle do not properly handle ServletRequest.getPathInfo() == null
> -----------------------------------------------------------------------------------------------
>
> Key: FELIX-1999
> URL: https://issues.apache.org/jira/browse/FELIX-1999
> Project: Felix
> Issue Type: Bug
> Affects Versions: http-2.0.4
> Reporter: Felix Meschberger
> Assignee: Felix Meschberger
> Fix For: http-2.0.6
>
>
> ServletRequest.getPathInfo() is allowed to return null (if there is no additional path information).
> For example, IBM WebSphere returns null if the client accesses the Servlet context without a trailing slash (Jetty in this case redirects to the context path with a trailing slash and thus this case does not happen).
> To prevent NullPointerExceptions from happening the FilterHandler.match and ServletHandler.match methods must guard against the uri parameter being null
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Work started: (FELIX-1999) The classes in the http.base
bundle do not properly handle ServletRequest.getPathInfo() == null
Posted by "Felix Meschberger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-1999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Work on FELIX-1999 started by Felix Meschberger.
> The classes in the http.base bundle do not properly handle ServletRequest.getPathInfo() == null
> -----------------------------------------------------------------------------------------------
>
> Key: FELIX-1999
> URL: https://issues.apache.org/jira/browse/FELIX-1999
> Project: Felix
> Issue Type: Bug
> Affects Versions: http-2.0.4
> Reporter: Felix Meschberger
> Assignee: Felix Meschberger
> Fix For: http-2.0.6
>
>
> ServletRequest.getPathInfo() is allowed to return null (if there is no additional path information).
> For example, IBM WebSphere returns null if the client accesses the Servlet context without a trailing slash (Jetty in this case redirects to the context path with a trailing slash and thus this case does not happen).
> To prevent NullPointerExceptions from happening the FilterHandler.match and ServletHandler.match methods must guard against the uri parameter being null
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.