cxf-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sergey Beryozkin <>
Subject Re: BaseUrlHelper bug (cxf 2.5.x -> 2.7.x) or Servlet Container bug?
Date Fri, 21 Feb 2014 11:48:23 GMT
Hi Alessio, Clint

I've just tried one of the JAX-RS tests, I got updated BaseUrlHelper to 
add a an extra slash in front of the context value so I have say "//the" 
as the context value, and I'm seeing 404 returned from the JAX-RS 
runtime, i.e, the "//" created at the BaseUrlHelper did not affect the 
endpoint selection process in the CXF HTTP transport module, but only 
the JAX-RS selection process.

Clint, I guess you need to follow the advice from Alessio if you are 
seeing the side-effects on the WS path, on the RS path you can register 
a JAX-RS 2.0 PreMatch ContainerRequestFilter and update the request URI 
from the filter if it has unexpected double slashes;


On 21/02/14 10:56, Alessio Soldano wrote:
> Hi,
> I agree with Sergey, this is something CXF should *not* directly deal with.
> Btw, I recently worked on a similar integration issue in JBossWS and
> made it possible to override the DestinationRegistryImpl#getTrimmedPath
> method [1]; that could possibly be used by the user here to provide a
> custom DestinationRegistry that properly deals with his edge case (I
> have something similar in JBossWS integration with Apache CXF).
> Cheers
> Alessio
> [1]
> On 20/02/14 22:14, Sergey Beryozkin wrote:
>> Hi
>> It is not a CXF bug and I don't think CXF should start messing with
>> replacing whatever HttpServletRequest container returns.
>> We can end up with the inconsistency introduced into the flow,
>> example, CXF
>> will remove the 'redundant' "/", then the code injected with
>> HttpServletRequest will see a "//", this can also be hidden but I
>> doubt we
>> can hide the actual request URI.
>> In fact, when we have something like "//cxf" then how we can even know
>> "/"
>> is redundant, it can be a context itself, a single "/", "//" is a
>> perfectly
>> valid path component value, meaning if we get rid of the first "/" we can
>> end up reporting a wrong context, "/cxf".
>> What happens when you see HttpServletRequest reporting
>> "//cxfservices", how
>> do you see it affecting the actual invocation ?
>> Sergey
>> --
>> View this message in context:
>> Sent from the cxf-user mailing list archive at

Sergey Beryozkin

Talend Community Coders


View raw message