| SmartBear Support wrote: |
|---|
| We will remove the application/x-pointplus one in next release. |
Thanks Joel. I was hoping to demo our API to clients using a SoapUI mock with a Swagger UI frontend in the next few days.
I could, of course, easily run the Swagger UI from a different server, but I have encountered a different issue when I do that - the CORS pre-flight OPTIONS request sent when I do a POST from the Swagger UI is declined, even if I set the correct headers:
"Access-Control-Allow-Origin" "*"
"Access-Control-Allow-Methods" "POST, GET, OPTIONS, PUT, PATCH, DELETE"
I am not sure if that is a Swagger problem or a SoapUI problem. But could you suggest a workaround for my original problem so I could use Swagger in the way I was hoping to? If I built SoapUI myself, but removed the reference to application-x/pointplus, would that work?
Thanks,
Christopher
