Friendly URL for my clients on OWA
Hi there
I have an OWA url of https://webmail.mydomain.com/owa and I would like to give them a friendly url of say www.mydomain.com/webmail that will then go to the https connection is this possible? And any idea how to do it please?
Cheers
February 16th, 2011 10:06am
If the www host is configured elsewhere then you just need to create a page to do a redirect.
Create a directory on your web host called webmail, then create a file called index.htm and copy this code in to it. Adjust the URL as required.
<html>
<head>
<meta http-equiv="REFRESH" content="0; URL=https://webmail.example.com/owa">
<title>Redirect</title>
</head>
<body>
<p><a href="https://webmail.example.com/owa">Redirect</a></p>
</body>
</html>
Simon Butler, Exchange MVP
Blog |
Exchange Resources | In the UK?
Hire Me.
Free Windows Admin Tool Kit Click here and download it now
February 16th, 2011 10:11am
errm! Doesn't that defeat the object of having an SSL then? I mean a simple redirect this way is compromising the orginal SSL, no?
February 16th, 2011 10:32am
Why would it?
They connect to an insecure connection, which then directs them to a secure connection to login.
If you don't want them to type https:// then you are going to have to put some code somewhere that lives on a regular web site.
Simon.Simon Butler, Exchange MVP
Blog |
Exchange Resources | In the UK?
Hire Me.
Free Windows Admin Tool Kit Click here and download it now
February 16th, 2011 10:41am
Sorry I think I must be missing something here. If they connect to an index.html file which is insecure then it's at that point that the url can hijacked to point to another url that mimicks our secure https url? But I'm trying to get the connection between
the friendly url and the https secure.
Cheers
February 16th, 2011 11:16am
Anything you do is going to be exposed to a man in the middle attack. Only by a direct connection to the server on its original address is going to change that. Although if you are really picky, any connection can be attacked via DNS poisoning etc. This
is where you have to take in to account user convenience versus network security.
There aren't really many other options. To go to secure URL users either need to type in, or click on a link that start https:// - there are various ways they can get there.
Simon.Simon Butler, Exchange MVP
Blog |
Exchange Resources | In the UK?
Hire Me.
Free Windows Admin Tool Kit Click here and download it now
February 16th, 2011 11:39am
Sembee
Does this article explain what I want to achieve or am I missunderstanding what I want: http://support.microsoft.com/kb/839357/en-us
cheers
February 17th, 2011 3:43am
That requires two things.
1. The host name that you are using to point to the Exchange server. If you want to use the www variant that means your public web site on a private server - not something that is good practise.
2. Port 80 open to the Exchange server. Again not a good practise. I don't want to encourage that kind of traffic to the server.
It is pretty much the same as what I have suggested, except the redirect page is on the same server.
Simon.Simon Butler, Exchange MVP
Blog |
Exchange Resources | In the UK?
Hire Me.
Free Windows Admin Tool Kit Click here and download it now
February 17th, 2011 11:43am
This topic is archived. No further replies will be accepted.
Other recent topics
