Question

I’m working through the final issues of an application set to go live this week. I need help to either modify my code or explain to our hosters what they need to fix in the IIS/DNS configurations to make this code work as expected.

Here is the code:

public string BaseSiteUrl
{
    get
    {
        var c = this.ControllerContext.RequestContext.HttpContext;
        string baseUrl = c.Request.Url.Scheme + "://" + c.Request.Url.Authority
                       + c.Request.ApplicationPath.TrimEnd('/') + '/';
        return baseUrl;
    }
}

I make a call to this in my Controller, to generate a url that gets persisted to a database.

It works fine when I run on my local machine. However, it does not work when it is run on the beta server.

Expected results on beta. On the beta server this is an application named dr405

• https://beta.sc-pa.com/dr405/

The actual result on beta. (I changed the server/domain names to what you see in CAPS for security’s sake)

• http://SERVERNAME1.GROUP1.SUBGROUP.local/dr405/

Answer 1

Due to time constraints, and the need to get this project out the door, I had to resort to hardcoding the main part of the url into the application. After I made the change I felt stupid for trying to make it dynamic in the first place. I mean how often should our domain name change?