ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-22680) Ambari web UI does not fail an invalid repo base URL during cluster installation
Date Thu, 21 Dec 2017 21:26:00 GMT

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

Hudson commented on AMBARI-22680:
---------------------------------

SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #8544 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8544/])
AMBARI-22680 Ambari web UI does not fail an invalid repo base URL during (dili: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=a15fc7fc1ac70d3399a1b4046c3124dcc8cdbb11])
* (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/internal/RepositoryResourceProvider.java
* (edit) ambari-server/src/test/java/org/apache/ambari/server/controller/internal/RepositoryResourceProviderTest.java


> Ambari web UI does not fail an invalid repo base URL during cluster installation
> --------------------------------------------------------------------------------
>
>                 Key: AMBARI-22680
>                 URL: https://issues.apache.org/jira/browse/AMBARI-22680
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: trunk
>            Reporter: Di Li
>            Assignee: Di Li
>             Fix For: trunk
>
>         Attachments: AMBARI-22680.patch
>
>
> This is because the Ambari server backend never validated anything. It just  simply sent
back HTTP 200 as a dummy response.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message