You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Http End point the path shows as the https://servername/api/workflows/ but it suppose to show path as https://servername/new/WorkflowApp/api/workflows/
Reproduction Rate:
"every time"
Expected Behavior
It suppose to show path URL as https://servername/new/WorkflowApp/api/workflows/
Actual Behavior
It suppose to show path URL as https://servername/new/WorkflowApp/api/workflows/
Environment
Elsa Package Version: 3.2.3 Elsa core and 3.2.2 Elsa Studio
Operating System: Windows server 2019
Browser and Version: Chrome 130 and Edge
Troubleshooting Attempts
Updated the "BaseUrl":"https://servername/ and "BasePath":"/api/workflows/new/WorkflowApp"
In this case HttpEndPoint activity referring correct URL(https://servername/new/WorkflowApp/api/workflows/) but when calling this API from api tools like Postman getting the 404 error.
The text was updated successfully, but these errors were encountered:
Description
HttpEndPoint activity referring wrong URL
Steps to Reproduce
Hosted the Elsa application in the IIS as below path
https://servername/new/WorkflowApp/
Configured the appsetting.json as below
"Http": {
"BaseUrl":"https://servername/new/WorkflowApp/",
"BasePath":"/api/workflows"
}
Http End point the path shows as the
https://servername/api/workflows/
but it suppose to show path ashttps://servername/new/WorkflowApp/api/workflows/
"every time"
Expected Behavior
It suppose to show path URL as
https://servername/new/WorkflowApp/api/workflows/
Actual Behavior
It suppose to show path URL as
https://servername/new/WorkflowApp/api/workflows/
Environment
Troubleshooting Attempts
In this case HttpEndPoint activity referring correct URL(https://servername/new/WorkflowApp/api/workflows/) but when calling this API from api tools like Postman getting the 404 error.
The text was updated successfully, but these errors were encountered: