Webservice calls and CORS

I've created some webservices that use a passed JSON variable in the content section of the httprequest. All works fine when I call from windev code in another app. However I wrote some javascript to call it, and it works fine on localhost, but when I call it on a production server, the javascript call fails with a CORS error. Using apache server.
I tried using 'no-cors' mode in the call, but then I can't use JSON in the content.
Anyone know how I can resolve this? I'd like to stick to using JSON content in the call.



Edited 1 time(s). Last edit at 08/25/2023 08:11AM by pauly139.

Following on, I've tried modifying the conf file in apache with the line

Header set Access-Control-Allow-Origin "*"

but obviously I'm not putting it in the right place. Anyone know where it goes in relation to the WB App Server entries?

Hi Pauly

This is the way to do it:
- Add an 'options' method to your post/get/... web service definition.
See Afbeelding1.png
- In there you do a call to set the CORS options for the endpoint.
See Afbeelding2.png

Cheers

Peter

Hi Pete - thanks for jumping in and helping out.

I added then OPTIONS method, and same code, but still no joy.

Does the apache conf file need any corresponding changes? Does it matter where the associated procedure for the OPTIONS method is (mine is in a global procedure)?

One clue is I put some trace code in that procedure, and it seems it is never executed.

Thanks for helping out...

Rgds
Paul



Edited 1 time(s). Last edit at 08/26/2023 12:22AM by pauly139.

Continuing the saga - I can see the http Header coming back correctly - see attached screenshots, but still the CORS error fires. I've also posted the javascript code calling the service. Perhaps the problem is my javascript (wouldn't be surprised :-))

Thanks to anyone who takes the time to have a look.