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.


On Fri, Feb 21, 2014 at 9:59 AM, Kevin Minder (JIRA) <[email protected]>wrote:

>
>      [
> https://issues.apache.org/jira/browse/KNOX-274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel]
>
> Kevin Minder updated KNOX-274:
> ------------------------------
>
>     Comment: was deleted
>
> (was: Hey Larry,
> Please comment in the jira.
> Kevin.
>
>
>
> --
> CONFIDENTIALITY NOTICE
> NOTICE: This message is intended for the use of the individual or entity to
> which it is addressed and may contain information that is confidential,
> privileged and exempt from disclosure under applicable law. If the reader
> of this message is not the intended recipient, you are hereby notified that
> any printing, copying, dissemination, distribution, disclosure or
> forwarding of this communication is strictly prohibited. If you have
> received this communication in error, please contact the sender immediately
> and delete it from your system. Thank You.
> )
>
> > 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)
>

Reply via email to