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

Robert Joseph Evans commented on HADOOP-8922:
---------------------------------------------

Damien, I put the patch into trunk, but it did not merge that cleanly into 
branch-2. It looks like there are a number of fixes that went into trunk that 
have not made it into branch 2.  If you could provide a patch for branch-2 that 
would be great.
                
> Provide alternate JSONP output for JMXJsonServlet to allow javascript in 
> browser dashboard
> ------------------------------------------------------------------------------------------
>
>                 Key: HADOOP-8922
>                 URL: https://issues.apache.org/jira/browse/HADOOP-8922
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: metrics
>    Affects Versions: 2.0.0-alpha
>            Reporter: Damien Hardy
>            Priority: Trivial
>              Labels: newbie, patch
>         Attachments: HADOOP-8922-3.patch, test.html
>
>
> JMXJsonServlet may provide a JSONP alternative to JSON to allow javascript in 
> browser GUI to make requests.
> For security purpose about XSS, browser limit request on other 
> domain[¹|#ref1] so that metrics from cluster nodes cannot be used in a full 
> js interface.
> An example of this kind of dashboard is the bigdesk[²|#ref2] plugin for 
> ElasticSearch.
> In order to achieve that the servlet should detect a GET parameter 
> (callback=xxxx) and modify the response by surrounding the Json value with 
> "xxxx(" and ");" [³|#ref3]
> value "xxxx" is variable and should be provide by client as callback 
> parameter value.
> {anchor:ref1}[1] 
> https://developer.mozilla.org/en-US/docs/Same_origin_policy_for_JavaScript
> {anchor:ref2}[2] https://github.com/lukas-vlcek/bigdesk
> {anchor:ref3}[3] http://en.wikipedia.org/wiki/JSONP

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to