Incorrect Request Dispatching

[Greg Logan <gr...@gmail.com>]

Hi,

I'm from the Opencast project (opencast.org), which uses Karaf, and CXF
among other frameworks.  We're seeing an issue where requests to a
non-existent endpoint are being dispatched to the alphabetically first
endpoint which matches the request parameters.  For instance, GETting
/info/{int}, which does not exist, gets you admin-ui/acl/{int}.

I've run through the stack trace, and I think I've narrowed it down to
JAXRSUtils:431.  I'm not sure where to go from here.  We're using CXF 3.2.6
at the moment, but 3.2.8 exhibits the same behaviour.  3.3.0 causes issues
on startup, so I haven't been able to test it, but the diff between 3.2.8
and 3.3.0 doesn't seem like it would change anything from 3.2.8.

How do I enforce that non-existent REST endpoints 404?

Thanks,
G

Re: Incorrect Request Dispatching

[Colm O hEigeartaigh <co...@apache.org>]

Can you create a test-case to reproduce the issue that we can look at?

Colm.

On Wed, Feb 13, 2019 at 5:25 PM Greg Logan <gr...@gmail.com> wrote:

> Hi,
>
> I'm from the Opencast project (opencast.org), which uses Karaf, and CXF
> among other frameworks.  We're seeing an issue where requests to a
> non-existent endpoint are being dispatched to the alphabetically first
> endpoint which matches the request parameters.  For instance, GETting
> /info/{int}, which does not exist, gets you admin-ui/acl/{int}.
>
> I've run through the stack trace, and I think I've narrowed it down to
> JAXRSUtils:431.  I'm not sure where to go from here.  We're using CXF 3.2.6
> at the moment, but 3.2.8 exhibits the same behaviour.  3.3.0 causes issues
> on startup, so I haven't been able to test it, but the diff between 3.2.8
> and 3.3.0 doesn't seem like it would change anything from 3.2.8.
>
> How do I enforce that non-existent REST endpoints 404?
>
> Thanks,
> G
>


-- 
Colm O hEigeartaigh

Talend Community Coder
http://coders.talend.com