Can't this redirect just be done at the hoster and point to the same IP
before it even gets to IIS?

On Tuesday, 3 November 2015, David Connors <[email protected]> wrote:

> +1 to Stephen's advice.
>
> I also wouldn't do the routing as a function of the MVC app. Use IIS
> Rewrite module and just make it part of the config (you can put the rules
> in your web.config so they deploy with your app). IIS Rewrite module is
> amazeballs.
>
> On Tue, 3 Nov 2015 at 14:23 Stephen Price <[email protected]
> <javascript:_e(%7B%7D,'cvml','[email protected]');>> wrote:
>
>> Personally, I'd pick the domain name you want people to use and get SSL
>> for that. Then the other domain name is just to catch people who went to
>> that one instead and route all your traffic to the main one.
>> If you have just two domain names then I can understand the questionmark
>> over how to use both. If you imagine adding a bunch more domain names (you
>> might have some alternate names to help catch more traffic) and route them
>> all to the main domain then it makes more sense. If you had 10 domain names
>> you wouldn't want an SSL for every one of them. Redirect is the way to go,
>> IMHO.
>>
>> On Tue, 3 Nov 2015 at 04:37 Greg Low (罗格雷格博士) <[email protected]
>> <javascript:_e(%7B%7D,'cvml','[email protected]');>> wrote:
>>
>>> Yes I wondered about that one - just seemed over the top. Initial page
>>> doesn't need SSL so might look at DNS redirect from .com.au to .com.
>>>
>>> Regards
>>>
>>> Greg
>>>
>>> Dr Greg Low
>>> SQL Down Under
>>> +61 419201410
>>> 1300SQLSQL (1300775775)
>>>
>>> On 3 Nov 2015, at 6:58 AM, Paul Glavich <[email protected]
>>> <javascript:_e(%7B%7D,'cvml','[email protected]');>> wrote:
>>>
>>> Actually, maybe this would suit you better
>>> https://www.digicert.com/unified-communications-ssl-tls.htm
>>>
>>>
>>>
>>> -          Glav
>>>
>>>
>>>
>>> *From:* [email protected]
>>> <javascript:_e(%7B%7D,'cvml','[email protected]');> [
>>> mailto:[email protected]
>>> <javascript:_e(%7B%7D,'cvml','[email protected]');>] *On
>>> Behalf Of *Greg Low (??????)
>>> *Sent:* Monday, 2 November 2015 9:08 PM
>>> *To:* ozDotNet <[email protected]
>>> <javascript:_e(%7B%7D,'cvml','[email protected]');>>
>>> *Subject:* RE: SSL Certs
>>>
>>>
>>>
>>> I suppose a more basic question is:
>>>
>>>
>>>
>>> What’s the cleanest way in an Azure website MVC app to route all
>>> requests for abcdef.com.au to abcdef.com ?
>>>
>>>
>>>
>>> Regards,
>>>
>>>
>>>
>>> Greg
>>>
>>>
>>>
>>> Dr Greg Low
>>>
>>>
>>>
>>> 1300SQLSQL (1300 775 775) office | +61 419201410 mobile│ +61 3 8676 4913
>>> fax
>>>
>>> SQL Down Under | Web: www.sqldownunder.com
>>>
>>>
>>>
>>> *From:* Greg Low (罗格雷格博士)
>>> *Sent:* Monday, 2 November 2015 9:03 PM
>>> *To:* ozDotNet <[email protected]
>>> <javascript:_e(%7B%7D,'cvml','[email protected]');>>
>>> *Subject:* SSL Certs
>>>
>>>
>>>
>>> Hi Guys,
>>>
>>>
>>>
>>> If using two domains like:
>>>
>>>
>>>
>>> abcdef.com
>>>
>>> and
>>>
>>> abcdef.com.au
>>>
>>>
>>>
>>> (and obviously the site also has the www. versions of those too).
>>>
>>>
>>>
>>> For SSL on Azure websites, thoughts on whether we should do two certs,
>>> or just do that on one of them and then do some sort of redirect for the
>>> other one? (It’s MVC)
>>>
>>>
>>>
>>> TIA,
>>>
>>>
>>>
>>> Regards,
>>>
>>>
>>>
>>> Greg
>>>
>>>
>>>
>>> Dr Greg Low
>>>
>>>
>>>
>>> 1300SQLSQL (1300 775 775) office | +61 419201410 mobile│ +61 3 8676 4913
>>> fax
>>>
>>> SQL Down Under | Web: www.sqldownunder.com
>>>
>>>
>>>
>>> --
> David Connors
> [email protected] | @davidconnors | LinkedIn | +61 417 189 363
>

Reply via email to