[
https://issues.apache.org/jira/browse/KNOX-274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13908421#comment-13908421
]
Larry McCay commented on KNOX-274:
----------------------------------
It probably does make more sense to allow it to be based on root context
and to be able to have separate default topologies for them (admin/api).
If we were to document an api like that it might be a little odd since we
don't have a specific context for it - but it sort of works too.
http://localhost:8443/{root context}/api/v1/stop
maybe it would be better as:
http://localhost:8443/{root context}/knoxapi/v1/stop
I don't have a strong opinion here - either way works.
> Reserve admin and api context paths for internal use
> ----------------------------------------------------
>
> Key: KNOX-274
> URL: https://issues.apache.org/jira/browse/KNOX-274
> Project: Apache Knox
> Issue Type: New Feature
> Components: Server
> Affects Versions: 0.3.0
> Reporter: Kevin Minder
>
> We should reserve a few top level context paths for future use. I'm thinking
> /admin and /api. This would allow us later to provide an admin ui and api on
> these paths without having to worry about conflicting with user's topology
> files.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
