HardServerUrl
No edit summary
No edit summary
Line 10: Line 10:
  <root HardServerUrl="<nowiki>https://theaddressyouwantyourapplicationtohave</nowiki>"></root>
  <root HardServerUrl="<nowiki>https://theaddressyouwantyourapplicationtohave</nowiki>"></root>
When setting the hardserverurl in systems that also use Turnkey you should(possibly) also make sure turnkey use the proper url to mdriven server by setting the [[MDrivenServerOverride]].xml settings.
When setting the hardserverurl in systems that also use Turnkey you should(possibly) also make sure turnkey use the proper url to mdriven server by setting the [[MDrivenServerOverride]].xml settings.
'''SignalR issue''': Setting HardServerUrl for the TurnkeyApplication effects the SignalRConnection so it may be required to make your Application find itself under the local server address rather than some reverseproxy address used in calling it.


This functionality is available in builds from 2019-04-17
This functionality is available in builds from 2019-04-17

Revision as of 10:41, 13 September 2021

MDriven Server (and TurnkeyServer) adapts by looking at the incoming requests to discern what its own address is.

In certain situations this is not desired.

One example is if you have the application behind a load balancer or reverse proxy and the load balancer pings your app with an address that is not the desired server address.

This could lead to your app getting confused to what its true url should be.

To mitigate this you can create a App_Data/HardServerUrl.xml file with content like this:

<root HardServerUrl="https://theaddressyouwantyourapplicationtohave"></root>

When setting the hardserverurl in systems that also use Turnkey you should(possibly) also make sure turnkey use the proper url to mdriven server by setting the MDrivenServerOverride.xml settings.

SignalR issue: Setting HardServerUrl for the TurnkeyApplication effects the SignalRConnection so it may be required to make your Application find itself under the local server address rather than some reverseproxy address used in calling it.

This functionality is available in builds from 2019-04-17

You can verify that the HardServerUrl is in effect by looking here:

2019-04-17 11h11 17.png
This page was edited 80 days ago on 02/10/2024. What links here