IIS hosting only supports site root for ARR proxy

[rlaveycal]

Symptoms

ServicePulse does not receive updates from the ServiceControl

Who is affected

Any user attempting to install ServicePulse using ARR proxy in a non-root directory.

POA

• Update ServicePulse SignalR version to latest stable. Signalr 2.2.0 #345
• Smoke Test ServiceControl / ServicePulse
• [ ] Create new release of ServicePulse
• [ ] Announcement

User Report:

Following the instructions to install under IIS (http://docs.particular.net/servicepulse/install-servicepulse-in-iis) works so long as the api proxy folder to service control is in the site root. If it's not (e.g. to host multiple service pulse instances talking to multiple service control instances) then the SignalR connect and related calls don't respect the correct URL and continue to use `/api/messagestream'

E.g. with service pulse installed in a /ServicePulse folder IIS logs show

GET /servicepulse/api/messagestream/negotiate _=1462878929505&X-ARR-CACHE-HIT=0&X-ARR-LOG-ID=6425b0eb-624e-4787-a75d-cbe5b3696c9d&SERVER-STATUS=200 80 - ::1 Mozilla/5.0+(Windows+NT+6.3;+WOW64;+Trident/7.0;+rv:11.0)+like+Gecko http://localhost/servicepulse/ 200 0 0 0
GET /api/messagestream/connect transport=webSockets&connectionToken=AQAAANCMnd8BFdERjHoAwE%2FCl%2BsBAAAApuf%2B71QcnkWoqd1F9VXo4QAAAAACAAAAAAAQZgAAAAEAACAAAAA2oYDR7QjczTdf3cpMDI2gDzSfz3RbU1L2btfR2FL3ngAAAAAOgAAAAAIAACAAAACCjaerwjgwdaN6v6MEYfRqMu179Zp2u6K6UmEkXHNN0jAAAAB2Ib%2FO8P%2BvydfnS32GLZnxcdDwnuXVpJck%2FQLByz%2BVqFhfH4ZAf8E0guI2AVpXPxlAAAAA1%2FQsBAMgmlEAXIEm%2FagjdaHNptHUMYjDwFCvxZqevqY%2B47i%2F%2F37JHlXigdKpga9rabYZZLJNBGjE7%2BlJ2Y7G3A%3D%3D&tid=5&X-ARR-CACHE-HIT=0&X-ARR-LOG-ID=2458b1cd-0f84-4d84-9beb-0d5878920ae0&SERVER-STATUS=101 80 - ::1 Mozilla/5.0+(Windows+NT+6.3;+WOW64;+Trident/7.0;+rv:11.0)+like+Gecko - 502 5 2 0

[WilliamBZA]

Hi @rlaveycal

Can you please confirm what value you configured for the service_control_url parameter in app.constants.js? This needs to be configured to reflect the url that the application will be hosted in, so in your case would probably be /servicepuls/api or something similar.

[rlaveycal]

Yes, it's set as you can see from the IIS log output. negotiate is called on the correct URL but connect on the wrong one.

This could be a SignalR bug - Pulse is using a very old version (1.1.3).

[WilliamBZA]

For version 1.1.3 this value needs to be set in the config.js file.

If the value has been set in the config.js file and you're still seeing the incorrect behaviour, is it possible for you to upgrade to the latest version of ServiceControl and ServicePulse?

[rlaveycal]

I'm using the latest version of SC and SP. 1.1.3 refers to the version of SignalR being used by SP

[boblangley]

Added PR with SignalR update. Smoke tested against Particular/ServiceControl#724

[WilliamBZA]

Closed by #345

New release of Service Pulse and Service Control will be coming soon to address this.