[
https://issues.apache.org/jira/browse/YARN-3148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14534578#comment-14534578
]
Hadoop QA commented on YARN-3148:
---------------------------------
\\
\\
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:red}-1{color} | patch | 0m 0s | The patch command could not apply
the patch during dryrun. |
\\
\\
|| Subsystem || Report/Notes ||
| Patch URL |
http://issues.apache.org/jira/secure/attachment/12731429/YARN-3148.02.patch |
| Optional Tests | javadoc javac unit findbugs checkstyle |
| git revision | trunk / 241a72a |
| Console output |
https://builds.apache.org/job/PreCommit-YARN-Build/7805/console |
This message was 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
> Affects Versions: 2.7.0
> Reporter: Prakash Ramachandran
> Assignee: Varun Saxena
> Labels: BB2015-05-RFC
> Attachments: YARN-3148.001.patch, YARN-3148.02.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)
