A deployed REST-based IFS web service produces CORS errors when called from a browser-based app, and disabling browser web security (like Chrome's --disable-web-security flag) only works for local testing, not for real end users.

All FAQ questions / Integrations and APIs

Answer

Fix this at the web server/HTTP server level rather than relying on browser flags — add an Access-Control-Allow-Origin rule to the HTTP response headers for the relevant endpoint(s). Using a wildcard (Access-Control-Allow-Origin: *) allows any origin to call the service, which is simplest but appropriate mainly for genuinely public APIs; for anything more sensitive, scope this to a specific, known list of allowed origin URLs instead of a blanket wildcard, so only your actual client applications can call the service cross-origin. This server-side header configuration is what actually resolves CORS for real end users, since it doesn't depend on anything being changed in their own browser.

Documentation-based answer. Confirm the product and release before applying it. This answer has not been verified in an IFS environment.

← Browse Integrations and APIs questions