Mock Service: Cross-domain from JavaScript
I'm trying to use my Mock Service from JavaScript, however, in order for the browser to allow me to send cross-domain requests, i have to receive one http-message containing these three headers: Acce...
Forum Discussion
was this ever solved? i have a similar issue my client is telling me that they are not abel to send the 2nd request even thought i have modified the mock response to contain the proper header...
> Is it possible to change the headers on the errors?
Sorry, I'm a SoapUI newbie; I don't know the answer to this specific question.
However, for what it's worth, here's how I currently deal with CORS issues and SOAP/SoapUI:
- To entirely avoid CORS issues, I host static test web pages (that send Ajax requests) via the Docroot property of the SoapUI mock service. The web pages and the mock service share the same protocol, domain, and port: so, no CORS issues.
- To work around CORS issues, I use CORS Anywhere. (I recently stuck my pencil neck out and wrote answers to the following two related questions on Stack Overflow: "How does SoapUI bypass CORS issue when my ajax call can't do it?" and "How to use Cors anywhere to reverse proxy and add CORS headers".)
