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

Jonathan Eagles commented on YARN-4009:
---------------------------------------

[~vvasudev], I'm wondering one more thing. Instead of adding logic for 
disabling the log message, I was thinking about changing the logic in 
ApplicationHistoryServer. Seems like we could just modify the logic below to 
avoid double adding the cross origin filter. What do you think?

{code}
    if (!initializers.contains(CrossOriginFilterInitializer.class.getName())) {
      if(conf.getBoolean(YarnConfiguration
          .TIMELINE_SERVICE_HTTP_CROSS_ORIGIN_ENABLED, YarnConfiguration
              .TIMELINE_SERVICE_HTTP_CROSS_ORIGIN_ENABLED_DEFAULT)) {
        if (initializers.length() != 0) {
          initializers += ",";
        }
        initializers += CrossOriginFilterInitializer.class.getName();
        modifiedInitializers = true;
      }
    }

{code}

> CORS support for ResourceManager REST API
> -----------------------------------------
>
>                 Key: YARN-4009
>                 URL: https://issues.apache.org/jira/browse/YARN-4009
>             Project: Hadoop YARN
>          Issue Type: Bug
>            Reporter: Prakash Ramachandran
>            Assignee: Varun Vasudev
>         Attachments: YARN-4009.001.patch, YARN-4009.002.patch, 
> YARN-4009.003.patch, YARN-4009.004.patch, YARN-4009.005.patch, 
> YARN-4009.006.patch
>
>
> Currently the REST API's do not have CORS support. This means any UI (running 
> in browser) cannot consume the REST API's. For ex Tez UI would like to use 
> the REST API for getting application, application attempt information exposed 
> by the API's. 
> It would be very useful if CORS is enabled for the REST API's.



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

Reply via email to