O
oedev
Guest
We're on 10.2b and managed to work around this in a couple of different ways (in dev anyway) 1 - If you are using Angular and have a live server running (by default on locahost:4200), configure a proxy as per the examples here: medium.freecodecamp.org/the-best-ways-to-connect-to-the-server-using-angular-cli-b0c6b699716c 2 - if your API (i.e. the webpseed bit) is fronted by an Apache web-server, you can set the headers in the httpd.conf as follows (this still requires the changes that you've made to set the access control headers; Listen 80 DocumentRoot "${SRVROOT}" ServerName www.example.com # Other directives here Header set Access-Control-Allow-Origin " http://localhost:4200" Header set Access-Control-Allow-Credentials "true" Header set Access-Control-Allow-Headers "Origin, X-Requested-With, Content-Type, Accept"
Continue reading...
Continue reading...