Now submitting username & password to login page creates this error on hosting server Apache Unix –
I understood that the choice to use or not use CORS only applies to choosing a Mobile application for Node.js in Wappler. I don’t see why the server should now be looking for the Access Control header.
There are questions and different opinions about this CORS error in the forum but no conclusive direction of final resolution that I find.
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://myownwebsite.de/trainings/dmxConnect/api/trainings.php. (Reason: CORS header ‘Access-Control-Allow-Origin’ missing). Status code: 302.
This is the json from that api – which just looks up a table – no problems before today
"SecurityProviders/security2",
{
"name": "",
"module": "auth",
"action": "restrict",
"options": {
"provider": "security2",
"loginUrl": "/trainingslogin.php",
"forbiddenUrl": "/trainingslogin.php"
}
},