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/02/03 14:13:27 UTC
[jira] Resolved: (FELIX-2000) Pathinfo for servlets/filters with
relative path not correctly determined
[ https://issues.apache.org/jira/browse/FELIX-2000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Felix Meschberger resolved FELIX-2000.
--------------------------------------
Resolution: Duplicate
Fix Version/s: http-2.0.6
Assignee: Felix Meschberger
Closing duplicate.
> 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
> Assignee: Felix Meschberger
> Fix For: http-2.0.6
>
>
> 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.