felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Felix Meschberger (JIRA)" <j...@apache.org>
Subject [jira] Commented: (FELIX-2000) Pathinfo for servlets/filters with relative path not correctly determined
Date Sat, 23 Jan 2010 14:36:17 GMT

    [ https://issues.apache.org/jira/browse/FELIX-2000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12804086#action_12804086
] 

Felix Meschberger commented on FELIX-2000:
------------------------------------------

Congratulations and thanks for reporting the "Millenium Bug" ;-)

Have you looked at my second patch from FELIX-1979 ? This uses the servlet container's getPathInfo()
method and the just chops off the servlet registration alias to get at the correct path info
(In fact the calculatePathInfo method of the HTTP Bridge 2.0.4 release also has an encoding
problem reported in FELIX-1979).

> Pathinfo for servlets/filters with relative path not correctly determined 
> --------------------------------------------------------------------------
>
>                 Key: FELIX-2000
>                 URL: https://issues.apache.org/jira/browse/FELIX-2000
>             Project: Felix
>          Issue Type: Bug
>          Components: HTTP Service
>         Environment: Apache Tomcat 5.5; Apache Felix 2.0.4.
>            Reporter: J.W. Janssen
>
> We're currently running an Felix HTTP-filter inside a Tomcat WAR. This WAR has the HTTP
Proxy from Felix registered on a relative path (for example '/osgi'). When trying to use the
Felix webconsole, one would suspect to have to use an URI like '/osgi/system/console'. However,
this is not working. 
> After some debugging, I came to the conclusion that the problem is caused by the implementation
of ServletHandlerRequest#calculatePathInfo() (in the http-base bundle). This method does not
take the relative paths of a servlet/filter into account to determine the path-info. Instead,
it assumes the servlet/filter has no relative path at all. Due to this, the webconsole retrieves
an incorrect URL and refuses to display as the webconsole uses the path-info for determining
which page (bundles, configuration, ...) it has to display.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message