For compatibility with IIS subsites, a user should be able to use an HTTP Endpoint activity which respects the base URL

In my environment, I have Elsa running as a subsite. Essentially, my asp web Elsa proj is in a subdirectory.

Example:
Base: mywebsite.com
Elsa: mywebsite.com/elsa
Elsa dashboard: mywebsite.com/esla/Elsa/home
Other apps I run: mywebsite.com/appname

This does not seem to play nicely with Elsa when creating a HTTP trigger to execute a workflow. I have tried almost everything I think.

I have tried setting the BaseUrl to mywebsite.com/elsa for the HttpActivities configuration.

I also tried messing with relative and absolute paths the workflow triggers listen for. For example: /elsa/executemyworkflow, mywebsite.com/elsa/executemyworkflow and etc.

I can get everything to work locally using IIS express because it is not running as a subsite. So I can set the relative path of my http trigger to /executemyworkflow and it will work as expected. However, as stated, I cannot get it to work when I deploy it out to my server because of the subsite configuration I have setup.

Like I said, I have tried all different types of configuration. I even tried leaving the baseurl blank.

As you can see with Elsa Dashboard as well, I can't find any configuration to set so instead of being: mywebsite.com/elsa/Elsa/home, it can be mywebsite.com/elsa/home

Overall the goal is to be able to trigger an Http activity when it is deployed as a subsite on IIS (mywebsite.com/elsa/executemyworkflow).

Any ideas how to get around all of this?

Thank you and please let me know if you have any questions!