felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Anders Engström (JIRA) <j...@apache.org>
Subject [jira] [Commented] (FELIX-5219) Servlet Bridge does not work if not mounted as root servlet
Date Sat, 19 Mar 2016 15:45:33 GMT

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

Anders Engström commented on FELIX-5219:
----------------------------------------

I have a fix (that needs to be cleaned up a bit) that might solve the problem: https://github.com/metamorph/felix/commit/0625c38e572f02bfce42ae5ece5c3e9688c87a75

Basically - by using a request header that identifies a request a proxied request the Dispatcher
can drop the `servletPath` when resolving the servlet to dispatch to. Requests that comes
through the stand-alone Jetty container should still be dispatched with the servletPath untouched.

Not sure of the "Forward" header is suitable or not - maybe it can be a custom header.

[~cziegeler] - what's your thoughts on this?

> Servlet Bridge does not work if not mounted as root servlet
> -----------------------------------------------------------
>
>                 Key: FELIX-5219
>                 URL: https://issues.apache.org/jira/browse/FELIX-5219
>             Project: Felix
>          Issue Type: Bug
>          Components: HTTP Service
>    Affects Versions: http.proxy-3.0.0, http.bridge-3.0.0, http.bridge-3.0.2, http.bridge-3.0.4,
http.bridge-3.0.6
>            Reporter: Anders Engström
>
> As described in the email thread http://www.mail-archive.com/users%40felix.apache.org/msg17074.html
-- the Http Servlet Proxy/Bridge does not work when binding the Proxy Servlet something else
than {{/*}}.
> It seems that the bug was introduced in the 3.* versions - the proxy/bridge works as
expected with version {{2.3.2}}.
> I've created a reference project at https://github.com/metamorph/http-osgi-bridge that
demonstrates the bug.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message