Reputation: 335
I am having trouble with CORS in Wakanda and found this:
https://github.com/Wakanda/wakanda-issues/issues/21
The link above seems to indicate a fix for this bug is 1.0.3.
I am running Wakanda Enterprise 11.0.0.0.
Where may I get this fix?
Upvotes: 2
Views: 188
Reputation: 335
My Wakanda solution was upgraded from v10 to v11. This was the cause of CORS failing as the .waSettings file which defines CORS has moved locations in the upgrade.
The answer to CORS failing for me was to create a new Solution in v11, and copy into it the needed files.
CORS now works as advertised!
Upvotes: 2
Reputation: 3541
you specified 192.168.2.100:80
but you do not need the port number when using the default port 80; you should just use 192.168.2.100
. The configuration should look like this when using the default port:
See issue #42: CORS does not work if port 80 is specific in the domain list.
This comment on Issue #21 has a sample solution download that shows CORS working. In the sample, CORS is enabled on both ends so that both projects allow each other but this can be disabled on the parent side.
I just tested that sample solution (using http://127.0.0.1:8082 as shown in the comments) and it works for me using Wakanda Digital App Factory 1.0.3 (build 11.197492):
For now support for CORS only works when you do not add special headers to your requests
So make sure you are not setting any additional headers with http_request.setRequestHeader()
Community Edition is available at wakanda.github.io
Enterprise Edition is available at wakanda.io
If you think you have uncovered a new bug you can file a new issue on github.
Upvotes: 2