I’ve a following deployment configuration. I’ve Web Backend ASP.NET application that an application in a browser working with and Services ASP.NET application that the Backend app is querying for services. What rather untraditional in this configuration is that both applications are deployed into same IIS and website and reside in different AppPools.
The URL for the Backend application is
http://<host>/meiwi and for Services app
The browser opens SSE channel/subscription vs. Backend application. However, the heart beat URL that it receives on connection is defined
It’s happening because a call to
http://<host>/meiwi.services although the subscription was issued with
http://<host>/meiwi (according to Fiddler).
When a deployment configuration includes only one ASP.NET application the generation of the heart beat URL works correctly.
Does anyone have an idea what can be a reason for this weird behavior?
NOTE: Applications are running in different Application Pools.