Mailing-List: contact yarn-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: yarn-dev@hadoop.apache.org
Date: Wed, 3 Sep 2014 17:55:52 +0000 (UTC)
From: "Steve Loughran (JIRA)" <jira@apache.org>
To: yarn-dev@hadoop.apache.org
Message-ID: <JIRA.12715728.1400674282000.8138.1409766952159@Atlassian.JIRA>
In-Reply-To: <JIRA.12715728.1400674282000@Atlassian.JIRA>
References: <JIRA.12715728.1400674282000@Atlassian.JIRA>
 <JIRA.12715728.1400674282254@arcas>
Subject: [jira] [Resolved] (YARN-2086) AmIpFilter to support REST APIs
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/YARN-2086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Steve Loughran resolved YARN-2086.
----------------------------------
    Resolution: Won't Fix

you can't open the filter and keep the AM secure ... the only secure solution here is for the proxy to support the full set of HTTP verbs

> AmIpFilter to support REST APIs
> -------------------------------
>
>                 Key: YARN-2086
>                 URL: https://issues.apache.org/jira/browse/YARN-2086
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: webapp
>            Reporter: Steve Loughran
>
> The {{AmIpFilter}} doesn't like REST APIs, as all operations are redirected to the proxy as a 302. Even if the proxy did relay all verbs, the filter would need to return a 307 and hope the client was enable to re-issue the verb.
> The alternative is to have a dedicated part of the webapp to be unproxied, which we did with a custom filter to not relay "/ws/*", or even allow apps to register a rest endpoint directly, either in the AppReport data, or via the YARN-913 registry


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)