Question

Very simply, I have a property/method that builds an absolute path to an image like so:

    public String Url
    {
        get
        {
            Uri rv_uri = new Uri(Context.Request.Url, Path);
            return rv_uri.AbsoluteUri;
        }
    }

But, when the this property is accessed via HTTPS, the return value still shows an HTTP scheme. In testing, I’ve found that Context.Request.Url is “unaware” that it’s operating under SSL.

Any known bugs with Context.Request.Url?

I will otherwise suspect the load balancer our hosting provider has in place is mucking things up. If that’s the case, am I SOL?

Thanks!

Answer 1

Much of the time, SSL is only to the load balancer.

This is done to reduce the load on the web servers and most of the time there is not need of SSL behind the firewall.