-
August 6th, 2018, 08:23 AM
#2
Hi, This means that the access from your page to the Server is considered by the browser as a CORS request (probably because of the different port).
Consequently, the browser sends a preliminary (i.e. preflight) request to the Server to check if the latter accepts the CORS request.
However, the request is refused because of the presence of the "username" extra http header.
This can be fixed by configuring the Server to allow this header in CORS requests.
This is done in the <cross_domain_policy> block in the Server configuration file, by defining the "accept_extra_headers" attribute accordingly; it should look like:
accept_extra_headers="username"
Then restart the Server and retry (I know you succeeded).
All this matter should be independent from the edition or license with which the Server runs.
Similar Threads
-
By rvkvino in forum General
Replies: 3
Last Post: August 31st, 2018, 10:09 AM
-
By stephenallred in forum Client SDKs
Replies: 1
Last Post: June 7th, 2010, 11:13 AM
Tags for this Thread
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
All times are GMT +1. The time now is 10:11 AM.
Bookmarks