Exchange 2013: HTTP redirection issues with ECP virtual directory – /owa/ecp
When you try to access ECP on Exchange 2013, browser redirects to /owa/ecp and shows “Bad Request”
You will see this if HTTP redirection is applied on Default website and those settings got replicated to all Virtual directories underneath.
Let’s look at How to enable HTTP redirect on Exchange 2013.
To enable HTTP to HTTPS redirection on exchange 2013, on IIS VDir highlight Default website and click HTTP Redirect:
Change the settings as shown:
The issue addressed in this article will happen if the ECP Vdir has an HTTP redirect set on it:
Let’s recap the SSL Settings and HTTP redirect settings for all Virtual directories in Exchange 2013 and ensure it is set properly:
| Vitual Directory |
SSL enabled |
HTTP Redirect |
| Default website |
NO |
Yes |
| aspnet_client |
Yes |
NO |
| Autodiscover |
Yes |
NO |
| ecp |
Yes |
NO |
| EWS |
Yes |
NO |
| owa |
Yes |
NO |
| Microsoft-Server-ActiveSync |
Yes |
NO |
| OAB |
Yes |
NO |
| PowerShell |
NO |
NO |
| Rpc |
Yes |
NO |
Ratish Nair
Microsoft MVP | Exchange Server
Team @MSExchangeGuru
Keywords: Exchange server 2013 owa redirection issue, exchange 2013 ECP redirects to /owa/ecp
March 2nd, 2014 at 4:53 pm
Exchange 2013 Sp1 Coexistence with Exchange 2010 SP3 CU5 HTTP 500
I`m trying to make working OWA coexistence between Exchange 2013 SP1 and Exchange 2010 SP3 CU5.
When user login in to OWA where his mailbox is located on Exchange 2013 server it logon successful and owa opened. When i try to login to the same url with user whose mailbox is located on Exchange 2010 server i get Error http 50
The website cannot display the page : HTTP 500 »https://URLEXCHANGE2013/owa/auth.owa«
The same is, when i use https:// URLEXCHANGE2013/ecp?ExchClientVer=14
URL on Exchange 2013 are different as fro Exchange 2010.
I even tried to setup Internal URL for Exchange 2010 to bi set to »null ,Saem error
Exchange server 2013 Sp1 is installed on Windows server 2012 R2.
March 11th, 2014 at 3:35 pm
2013 and 2010 urls should be same and both should be in the same AD forest.
you can also keep same internal url.
With SP1 we have fixed all redirection issue.
Let us know how does it go.
July 20th, 2014 at 10:54 am
When you do this, one will lose access to ecp. How can I do this and maintain access to ecp?
Thanks.
July 28th, 2014 at 1:00 am
You should not loose ECP. We are stopping redirection.
October 15th, 2014 at 1:51 pm
I have a issue I want to use the server were Exchange 2013 is installed to act also as a normal web server. but nowadays when I do http://127.0.0.1 it doesn’t allow and asks to add https and then goes to OWA… how can I do change it?
Exchange OWA is working ok. Exchange 2013 is working ok.
My goal ultimate goal is to use the server also with wordpress.
Thanks in advance for your cooperation.
Regards
Mario
October 18th, 2014 at 2:39 pm
It is not recommended to use exchange server for another application. So Microsoft will not support this configuration.
How to do it is simply creating new website in iis with different port & url then on your firewall do a NAT+PAT.
November 7th, 2014 at 5:15 am
Hi, I have the same problem as “Mali stane” from the first comment above. Exchange 2013 on CU5, Exchange 2010 on latest update. I know that all redirection issues should be fixed with SP1 but obviously there are still problems. Any idea? Thanks.
November 8th, 2014 at 3:32 pm
I have an Exchange 2013 and want to use OWA on port 80 because port 443 is being used by something else. I disable SSL on both OWA VD on default and backend sites. Redirect is not enabled but for some reason whenever I go to the owa site it redirects me to https. It worked fine in Exchange 2010.
Any advice? Thanks!
November 12th, 2014 at 10:14 am
@Mali,
Are you saying you are still having redirection issue? Could you update your current infrastructure and what is the issue now?
December 1st, 2014 at 10:23 pm
@Jason
use 444 with SSL. You should use SSL.
February 16th, 2015 at 3:10 am
“RPC” virtual directory will NOT have SSL Required by default in Exchange 2013 cu7
September 7th, 2015 at 7:01 am
[…] turned out to be an issue with HTTP redirection in IIS and, following the MSExchangeGuru post on HTTP redirection issues with the ECP virtual directory I set up HTTP redirection on the Default Website but turned it off for OWA, ECP and the various […]
July 16th, 2016 at 6:22 am
Hi,
We have co-existing setup of exchange 2010 and 2013 in single site. on newly built exchange 2013 servers, whenever we are trying to access legacy mailbox from exchange 2013 OWA, it opened but in freeze mode. we are unable to doo anything. I tried to open from local host too and different-2 browsers but no luck.
please help
July 17th, 2016 at 2:10 pm
Freezing can happen because of many things. We would need to assess your infrastructure. Mail me if you need our pro services at prabhat.nigam@GoldenFive.net
August 31st, 2016 at 4:32 am
[…] These are very much same steps, we had explained for Exchange 2013 – https://msexchangeguru.com/2013/10/30/http-redirect-owa-ecp/ […]
January 5th, 2017 at 9:01 am
You are my hero. Finally I can use my ecp again. 🙂
April 26th, 2017 at 3:01 pm
I was searching for instructions on redirecting http to https for owa and saw your site. If i followed your instruction and it broke my outlook clients what would that mean? i did not touch exchange back end in IIS ..just Default Web site. I managed to get Outlook working again, i believe by undoing what i did wrong and deleting the webconfig file. But not OWA is in a login loop where i put in known good credentials and it circles back to the same page, then ECP does the same but that redirects to OWA login page after known good information is put in. I don’t want to touch anything until tonight when most users are off the system, so i don’t break Outlook again. 🙂
May 13th, 2017 at 12:24 am
Please ensure to follow the steps correctly.
July 12th, 2017 at 5:37 pm
Hola,
Yo uso un exchange server 2013, para owa puedo entrar y operar sin problema pero cuando hago cerra seccion me da el siguiente error : “ERR_TOO_MANY_REDIRECTS” he buscado y hecho todo y nada que puedo depurar este error
Espero su ayuda en tu tiempo
saludos
July 15th, 2017 at 3:03 am
Hola, Ktal,
I have seen this. if you redirect to the same url and it falls in the loop then you will see too many redirects. Last week I had fixed for a customer.