Re:Re: Phosphor Web-ui: Server unreachable - cross origin request blocked

Re:Re: Phosphor Web-ui: Server unreachable - cross origin request blocked

[Joseph Reynolds]

[-- Attachment #1: Type: text/plain, Size: 1691 bytes --]


On 8/7/2018 5:13 AM, AKASH wrote:
>
> Message: 4
> Date: Tue, 7 Aug 2018 15:43:21 +0530
> From: AKASH G J <akashgj91@gmail.com>
> To: Ed Tanous <ed.tanous@intel.com>
> Cc: openbmc@lists.ozlabs.org
> Subject: Re: Phosphor Web-ui: Server unreachable
> Message-ID:
> 	<CAE33tLHsd5HwrCS9qLXO6Mo_gzka1Mrv7vs3Ofy0AF=YRJdT1w@mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> Hi Ed,
>
> Sorry for the late reply. I was on leave for last week.
>
> I am hosting phosphor-webui on a different machine and trying to connect
> the BMC board using its IP address. I am using bmcweb platform. When I
> tried to login, the following message appeared in browser console.
>
> Cross-Origin Request Blocked: The Same Origin Policy disallows reading the
> remote resource at https://<BMC-IP>/login. (Reason: CORS request did not
> succeed).
> <unavailable> activity-stream.bundle.js:3170:9
> CSI/tbsd_ cb=gapi.loaded_0:458:127
> CSI/_tbnd cb=gapi.loaded_0:458:127
> CSI/tbsd_ cb=gapi.loaded_0:458:127
> CSI/_tbnd cb=gapi.loaded_0:458:127
See 
https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Access-Control-Allow-Origin.
I think the HTTP response header from phosphor-webui needs to include 
"Cross-origin resource sharing" headers such as:
Access-Control-Allow-Origin: <YOUR-WEB-HOSTING-MACHINE-IP>, 
<original-ip>    <-- or use *
   Access-Control-Allow-Credentials: true
   Access-Control-Allow-Methods: POST, GET, OPTIONS, DELETE
   Access-Control-Max-Age: 3600
   Access-Control-Allow-Headers: Content-Type, Accept, X-Requested-With, 
remember-me

How would we enhance the phosphor-webui application to produce these 
headers?

> Thanks and Regards,
>
> Akash
> [...snip...]


[-- Attachment #2: Type: text/html, Size: 3026 bytes --]