Cors Application Settings inconsistency for non 200 HTTP responses
Under Application Settings there is a section for "CORS Header" where you can enable to add the 'Access-Control-Allow-Origin:' header to responses. When enabling this setting any custom htaccess and even this setting is ignored and responses that are not 2xx (for instance a status 400) WILL NOT GET the proper header "access-control-allow-origin" set to * and therefore the response cannot be validated. We end up EVERYTIME we create a new server requesting to SUPPORT that they manually add the proper header to the Nginx setting...
1
vote
Browix Suite
shared this idea