Hey All,
After googling around a bit and some trial and error, I was able to find a work around for
the CORS issue. One can start up chrome using a disable web security flag[1]. As per the
link,
On OS X:
/Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome —disable-web-security
On Windows:
Chrome.exe —disable-web-security
The link also outlines steps for Firefox, but I haven’t tried it.
Brandon
[1]
https://blog.nraboy.com/2014/08/bypass-cors-errors-testing-apis-locally/
On Jun 14, 2015, at 11:39 AM, Brandon Gaisford <bgaisford(a)punagroup.com> wrote:
I’m following the Hawtio README, the setup seems fine and all is running.
Node starts:
$ gulp
[11:31:55] Server started
http://localhost:2772
[11:31:55] LiveReload started on port 35729
When I make updates in the Hawtio src tree, the server reloads, all looks good.
The gateway and apiman services are running:
GET:
http://localhost:8080/apiman/system/status (had to login)
{"up":true,"version":"1.1.4-SNAPSHOT"}
Decided to start up firebug in Firefox and see if I could seed anything. Looks like an
error early in UI startup:
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote
resource at
http://localhost:8080/apiman/system/status. (Reason: CORS header
‘Access-Control-Allow-Origin' missing).
What is the correct way to get around this CORS stuff during Node/Hawtio development?
Thanks,
Brandon
_______________________________________________
Apiman-user mailing list
Apiman-user(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/apiman-user