-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CORS OPTIONS headers not working when using a remote server #721
Comments
As per the readme please post questions to the mailing list. Also suggest posting a bit more detail about how you're calling the endpoint and how you loaded the mappings into the remote server. |
OK not making any more questions. I uploaded all my wiremock folder (including __files, mappings and a custom response folder for static response files) to the server. {
"priority":10,
"request": {
"method": "ANY",
"urlPattern": ".*"
},
"response": {
"status": 404,
"jsonBody": {"status":"Error","message":"Endpoint not found"},
"headers": {
"Content-Type": "application/json"
}
}
} The calls are being done through a Ionic app, using Angular. I'm debugging the app through the browser. No issues either in the browser. Please point me out if there's any other information you require to attend the issue (ignore the question about dirty workarounds). |
Even I am facing the same issue |
+1 |
Hi.
I'm currently using wiremock on a remote server outside my network.
Using the current configuration for the OPTIONS method like:
works perfectly if I'm connecting from the same network.
After uploading the same mapping files to a remote server, I'm getting this error message:
I currently solved it by duplicating my request mappings, changing the method to OPTIONS and deleting the response leaving only a status 200.
Is there any way to get CORS working without this dirty workarounds?
The text was updated successfully, but these errors were encountered: