tag:support.appharbor.com,2010-11-23:/discussions/problems/26534-why-isnt-aspnetusehostheaderforrequesturl-true-by-defaultAppHarbor: Discussion 2013-12-18T21:59:31Ztag:support.appharbor.com,2010-11-23:Comment/267545852013-05-08T16:47:03Z2013-05-08T16:50:22ZWhy isn't aspnet:UseHostHeaderForRequestUrl true by default?<div><p>Hello,</p>
<p>As I'm sure many users have, I ran into the issue where a port
number is incorrectly included in absolute URLs generated by the
framework. I found this <a href=
"http://support.appharbor.com/kb/getting-started/workaround-for-generating-absolute-urls-without-port-number">
KB article</a> and quickly threw in the new app setting. But then I
wondered why this isn't just taken care of for you by App Harbor by
default, i.e. AppHarbor automatically includes the setting if not
present in the build process. Is there some reason for it?
Thanks.</p></div>sbrown13tag:support.appharbor.com,2010-11-23:Comment/267545852013-05-09T00:50:16Z2013-05-09T00:50:45ZWhy isn't aspnet:UseHostHeaderForRequestUrl true by default?<div><p>Hi,</p>
<p>That's a good question. We actually tried to make it the default
a while back, but unfortunately a lot of apps are not compatible
with this setting. Particularly WCF apps had problems with this
configuration. That's the reason we reverted the change and added
it to the KB article instead.</p>
<p>Introducing new defaults is almost always a bit tricky
considering the volume and diversity of the apps deployed to
AppHarbor. We're considering various other approaches to alleviate
the issues related to running an IIS app in a load balanced setup,
and more generally, presenting recommended configurations that can
optionally be selected when creating the app.</p>
<p>Best,<br>
Rune</p></div>rune