[
https://issues.apache.org/jira/browse/YARN-3148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14307855#comment-14307855
]
Hadoop QA commented on YARN-3148:
---------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12696820/YARN-3148.001.patch
against trunk revision c4980a2.
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. There were no new javadoc warning messages.
{color:red}-1 eclipse:eclipse{color}. The patch failed to build with
eclipse:eclipse.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 2.0.3) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in .
Test results:
https://builds.apache.org/job/PreCommit-YARN-Build/6522//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/6522//console
This message is automatically generated.
> allow CORS related headers to passthrough in WebAppProxyServlet
> ---------------------------------------------------------------
>
> Key: YARN-3148
> URL: https://issues.apache.org/jira/browse/YARN-3148
> Project: Hadoop YARN
> Issue Type: Improvement
> Reporter: Prakash Ramachandran
> Assignee: Varun Saxena
> Attachments: YARN-3148.001.patch
>
>
> currently the WebAppProxyServlet filters the request headers as defined by
> passThroughHeaders. Tez UI is building a webapp which using rest api to fetch
> data from the am via the rm tracking url.
> for this purpose it would be nice to have additional headers allowed
> especially the ones related to CORS. A few of them that would help are
> * Origin
> * Access-Control-Request-Method
> * Access-Control-Request-Headers
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
