You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Tom Beerbower (JIRA)" <ji...@apache.org> on 2013/10/02 19:57:46 UTC

[jira] [Commented] (AMBARI-3430) Add verification for setting repository base URL

    [ https://issues.apache.org/jira/browse/AMBARI-3430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13784216#comment-13784216 ] 

Tom Beerbower commented on AMBARI-3430:
---------------------------------------

+1 on the patch.

> Add verification for setting repository base URL
> ------------------------------------------------
>
>                 Key: AMBARI-3430
>                 URL: https://issues.apache.org/jira/browse/AMBARI-3430
>             Project: Ambari
>          Issue Type: Task
>          Components: controller
>            Reporter: Nate Cole
>            Assignee: Nate Cole
>             Fix For: 1.4.2
>
>         Attachments: AMBARI-3430.patch
>
>
> The server should validate the base url for any repository.
> * Make a configuration property that indicates the repo suffixes to apply to a URL to verify it.  This can be a comma-separated value.  If none is specified, use {{/repodata/repomd.xml}}
> * The check should be tolerant of a trailing slash ('/') on the base_url.
> * Use a connection timeout of 3 seconds and a read timeout of 500ms.
> * If all suffixes fail, return a 400 response to the client.  If any suffix works, return a 200.
> * Optionally allow a request to indicate that a validity check can fail, but still set the value anyway.  This allows the caller to set a URL that is known to work from each node in the cluster, even if it is inaccessible to the Ambari server.



--
This message was sent by Atlassian JIRA
(v6.1#6144)