- Joined
- Jul 26, 2019
- Messages
- 32
- Reaction score
- 8
Note, I have added the following to the nginx configuration for testing purposes in an attempt to correct the situation, this worked in v18 but doesn't seem to in v20.
I have tried the previously working snippet in the following two sections of :
1. location ~ ^/webclient(?!(/api|3cx-worker.js))
2.See screenshot
I'll note I am able to create a meeting using Postman, this is of course because postman doesn't send a preflight request as it's a testing tool. As per web standards it's mandatory to have a preflight request approved by the API server. There does not seem to be anything within 3CX that would allow this, any insight would be appreciated.
Important note: for the purposes of my testing, an FQDN is not presently specified but is during production for obvious reasons.
I have tried the previously working snippet in the following two sections of :
1. location ~ ^/webclient(?!(/api|3cx-worker.js))
2.See screenshot
if ($request_method = 'OPTIONS') {
add_header 'Access-Control-Max-Age' 1728000;
add_header 'Access-Control-Allow-Origin' 'testing.domain.org';
add_header 'Content-Type' application/json;
add_header 'Content-Length' 1;
add_header 'Access-Control-Allow-Headers' '3CX-ApiKey, content-type';
add_header 'Access-Control-Allow-Methods' 'OPTIONS';
return 200;
}I'll note I am able to create a meeting using Postman, this is of course because postman doesn't send a preflight request as it's a testing tool. As per web standards it's mandatory to have a preflight request approved by the API server. There does not seem to be anything within 3CX that would allow this, any insight would be appreciated.
Important note: for the purposes of my testing, an FQDN is not presently specified but is during production for obvious reasons.
Attachments
Last edited: