Last post Oct 01, 2015 04:54 AM by Li Wang
Sep 30, 2015 01:39 PM|dotnetterAMG123|LINK
I have a WebAPI2 REST service that returns all test entities using testentities at the end of the url. A client consuming this web service reported that they were able to consume this method in Postman without issue. However, when they called this service
method from their app, they received the following error:
"XmlHttpRequest cannot load testentites. The request was redirected to testentites/, which is disallowed for cross-origin requests that require preflight."
The client later reported that they were able to get around the error above by simply calling the service method with a trailing "/" on the end but the standard format to get all entities from a rest service method doesn't use the trailing slash.
Any idea what the issue might be in the client app that would cause the app to require putting a trailing "/" at the end of the rest service method? Or is this a common requirement when calling rest service methods from certain types of applications?
Oct 01, 2015 04:54 AM|Li Wang|LINK
Or is this a common requirement when calling rest service methods from certain types of applications?
http://xx.xxx/ or http://xx.xxx/abc is the default format.