CORS Workaround
Comments
-
If you are using a front-end server that is not iframed inside of Decisions and you are trying to use Decisions flows, then you have probably hit an issue in your browser related to CORS: [url=https://developer.mozilla.org/en-US/docs/Web/HTTP/Access_control_CORS]https://developer.mozilla.org/en-US/docs/Web/HTTP/Access_control_CORS[/url]
Because of this, you will not be able to use the Decisions endpoints. Ive created a workaround for this and published it to GitHub: [url=https://github.com/jawa-the-hutt/Decisions-CORS-Proxy]https://github.com/jawa-the-hutt/Decisions-CORS-Proxy[/url]
Its a project written in C# that will allow you to create an ASP.NET WebAPI 2 endpoint that will proxy your request to the Decisions server. This endpoint is meant to be hosted on the same server as your front-end. Please read through the readme in the project for a full explanation of the issue and how to use the project.
If you have questions or problems then open an issue in the github repository and within reason, Ill try and help you.
Howdy, Stranger!
Categories
- 2.1K All Categories
- 18 General
- 155 Installation / Setup
- 991 Flows
- 86 Rules
- 203 Administration
- 204 Portal
- 433 General Q & A
- 600 Forms
- 282 Reports
- 3 Designer Extensions
- 38 Example Flows
- 32 CSS Examples
- 1 Diagram Tile
- 5 Javascript Controls
- 139 Pages
- 1 Process Mining
- New Features
- 150 Datastructures
- 50 Repository
- 169 Integrations
- 25 Multi-Tenant
- 21 SDK
- 40 Modules
- 38 Settings
- 20 Active Directory
- 12 Version 7
- 34 Version 8