Timeline for Obtaining a site url with correct binding port dynamically
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 23, 2017 at 14:23 | vote | accept | Elena P | ||
| Nov 15, 2016 at 13:10 | comment | added | Richard Seal♦ | My guess would be that there is some internal redirection happening, possibly behind a load balancer. If the external port is 44305 to the LB, but the LB then hits the origin server at port 8081, the code will only see the 8081 port. | |
| Nov 15, 2016 at 8:44 | comment | added | Elena P |
Thank you! Do you have an idea on why the Uri.Port that is added not the same that the one I actually use? My problem with Sitecore.Globals.ServerUrl is that I go to https://foo.bar:44305/whatever/page, change it, and the users get an e-mail notification that contains a wrong port, i.e.: "Hey, https://foo.bar:8081/whatever/page was changed, check it out."
|
|
| Nov 14, 2016 at 17:14 | history | answered | Richard Seal♦ | CC BY-SA 3.0 |