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
- 4.4K All Categories
- 80 General
- 13 Training
- 209 Installation / Setup
- 1.1K Flows
- 110 Rules
- 270 Administration
- 213 Portal
- 497 General Q & A
- 709 Forms
- 345 Reports
- 3 Designer Extensions
- 48 Example Flows
- 58 CSS Examples
- 1 Diagram Tile
- 7 Javascript Controls
- 186 Pages
- 5 Process Mining
- New Features
- 186 Datastructures
- 70 Repository
- 229 Integrations
- 29 Multi-Tenant
- 27 SDK
- 81 Modules
- 59 Settings
- 26 Active Directory
- 12 Version 7
- 35 Version 8
- 143 Lunch And Learn Questions