Correct. For example, our demo server: https://stable.opencast.org/info/501 returns (after logging in with the provided credentials) a JSON blob of an ACL. There is no endpoint /info/{int}. What's you're actually talking to is https://stable.opencast.org/admin-ng/acl/501, which happens to take a single integer and be a GET request endpoint, and be alphabetically first in our full list of endpoints :)
G On Fri, Feb 15, 2019 at 1:58 PM Jean-Baptiste Onofré <j...@nanthrax.net> wrote: > Hi Greg, > > Do you have a simple test case to reproduce it ? > > To be sure I understand, when you try GET on > http://host:8181/cxf/info/10 you go to > http://host:8181/cxf/admin-ui/acl/10 ("cxf" part of the URL can be > different depending of the CXF cfg file) ? > > Regards > JB > > On 15/02/2019 20:47, Greg Logan wrote: > > Hi all, > > > > I'm from the Opencast project (opencast.org <http://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 it's CXF, but my mail on > > that list hasn't gotten any traction so I figured I would expand my > > search. Is CXF what I'm looking for here? Or is it some other part of > > Karaf? > > > > Thanks, > > G > > -- > Jean-Baptiste Onofré > jbono...@apache.org > http://blog.nanthrax.net > Talend - http://www.talend.com >
