You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@knox.apache.org by "Kevin Minder (JIRA)" <ji...@apache.org> on 2014/02/21 14:19:19 UTC

[jira] [Created] (KNOX-274) Reserve admin and api context paths for internal use

Kevin Minder created KNOX-274:
---------------------------------

             Summary: 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)

Re: [jira] [Created] (KNOX-274) Reserve admin and api context paths for internal use

Posted by Kevin Minder <ke...@hortonworks.com>.
Hey Larry,
Please comment in the jira.
Kevin.

On 2/21/14 9:50 AM, larry mccay wrote:
> +1 - though I wonder why we don't make it knox/admin, knox/api...
>
>
> On Fri, Feb 21, 2014 at 8:19 AM, Kevin Minder (JIRA) <ji...@apache.org>wrote:
>
>> Kevin Minder created KNOX-274:
>> ---------------------------------
>>
>>               Summary: 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)
>>


-- 
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.

Re: [jira] [Created] (KNOX-274) Reserve admin and api context paths for internal use

Posted by larry mccay <la...@gmail.com>.
+1 - though I wonder why we don't make it knox/admin, knox/api...


On Fri, Feb 21, 2014 at 8:19 AM, Kevin Minder (JIRA) <ji...@apache.org>wrote:

> Kevin Minder created KNOX-274:
> ---------------------------------
>
>              Summary: 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)
>