Re: [Apiman-user] Hawtio Based API Manager UI Developer Setup Issues

This is a fine workaround for development, but I'm surprised you ran into a CORS problem. There should be a CORS filter enabled for /apiman allowing the UI to work across origins. I do this all the time when using gulp to develop the UI. What is your server setup? Are you using the standard WF8 distribution? If CORS is broken on the server we need to know. I'll go test it right now! :) -Eric On 6/15/2015 12:24 AM, Brandon Gaisford wrote: > > 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 > <mailto:bgaisford@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 <mailto:Apiman-user@lists.jboss.org> >> https://lists.jboss.org/mailman/listinfo/apiman-user > > > > _______________________________________________ > Apiman-user mailing list > Apiman-user(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/apiman-user >