Phosphor Web-ui: Server unreachable
Ed Tanous
ed.tanous at intel.com
Fri Aug 10 04:43:06 AEST 2018
> gives error in compilation of bmcweb. The following are some error
> messages I got.
I had a minor transcription typo in what I said in my email, and it
looks like chrome must've increased their security threshold since the
last time I tried this. I've done this the right way, and added these
headers (and a couple other things) under the
BMCWEB_INSECURE_DISABLE_XSS_PREVENTION option flag. To develop this way.
Check out this code review.
https://gerrit.openbmc-project.xyz/#/c/openbmc/bmcweb/+/11887
and add this to the bottom of bmcweb.bb
EXTRA_OECMAKE += "-DBMCWEB_INSECURE_DISABLE_XSS_PREVENTION=ON"
This can also be done in a bmcweb.bbappend file if you want to check it
into some kind of development meta layer.
That should build you a copy of bmcweb into your system image with the
XSS protections disabled, and the correct header responses for
developing phosphor-webui this way. I tried locally on my machine,
using the "npm run-script server" and it seemed to work correctly,
although I didn't poke too hard at it, so there may still be bugs here
or there.
If this works for you, it would be great if you could add your comments
to the code review above.
More information about the openbmc
mailing list