Back Midas Rome Roody Rootana
  Root Analyzer Framework  Not logged in ELOG logo
Entry  10 Mar 2016, Thomas Lindner, Info, web display of MIDAS data using rootana+THttpServer 
    Reply  25 Jan 2017, Thomas Lindner, Info, web display of MIDAS data using rootana+THttpServer 
       Reply  26 Jan 2017, Pierre Gorel, Info, web display of MIDAS data using rootana+THttpServer 
       Reply  03 May 2017, Alberto Remoto, Info, web display of MIDAS data using rootana+THttpServer 
          Reply  03 May 2017, Thomas Lindner, Info, web display of MIDAS data using rootana+THttpServer 
             Reply  09 May 2017, Konstantin Olchanski, Info, web display of MIDAS data using rootana+THttpServer 
                Reply  10 Mar 2020, Konstantin Olchanski, Info, web display of MIDAS data using rootana+THttpServer 
Message ID: 9     Entry time: 09 May 2017     In reply to: 8     Reply to this: 20
Author: Konstantin Olchanski 
Topic: Info 
Subject: web display of MIDAS data using rootana+THttpServer 
> 
> 2) The 'same-origin policy' means that you need to setup some sort of proxying so that the custom web page can access the 
> ROOT webpage.  So, let's suppose in your case that you had the following ports for web servers:
> [1] https://developer.mozilla.org/en-US/docs/Web/HTTP/Access_control_CORS
>

The MIDAS web server mhttpd already implements CORS, so you can access mhttpd AJAX and JSON-RPC from external web pages, no need to proxy.

Does the ROOT web server NOT implement CORS? We should file a bug report with ROOT if it does not.

K.O.
ELOG V3.1.4-2e1708b5