You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Devaraj K (JIRA)" <ji...@apache.org> on 2015/06/17 12:08:01 UTC
[jira] [Updated] (YARN-3148) Allow CORS related headers to
passthrough in WebAppProxyServlet
[ https://issues.apache.org/jira/browse/YARN-3148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Devaraj K updated YARN-3148:
----------------------------
Labels: (was: BB2015-05-RFC)
Summary: Allow CORS related headers to passthrough in WebAppProxyServlet (was: allow CORS related headers to passthrough in WebAppProxyServlet)
> 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
> Attachments: YARN-3148.001.patch, YARN-3148.02.patch, YARN-3148.03.patch, YARN-3148.04.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)