MSExchangeGuru.com

Learn Exchange the Guru way !!!

 

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

16 Responses to “Exchange 2013: HTTP redirection issues with ECP virtual directory – /owa/ecp”

  1. Mali stane Says:

    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.

  2. Prabhat Nigam Says:

    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.

  3. Pedro Branco Says:

    When you do this, one will lose access to ecp. How can I do this and maintain access to ecp?

    Thanks.

  4. Prabhat Nigam Says:

    You should not loose ECP. We are stopping redirection.

  5. Mario Says:

    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

  6. Prabhat Nigam Says:

    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.

  7. Mali Stane Says:

    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.

  8. Jason Says:

    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!

  9. Prabhat Nigam Says:

    @Mali,
    Are you saying you are still having redirection issue? Could you update your current infrastructure and what is the issue now?

  10. Prabhat Nigam Says:

    @Jason
    use 444 with SSL. You should use SSL.

  11. Moin MD Says:

    “RPC” virtual directory will NOT have SSL Required by default in Exchange 2013 cu7

  12. Looping on the authentication prompt for the ECP virtual directory in Exchange 2013 - markwilson.it Says:

    […] 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 […]

  13. Manjeet Says:

    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

  14. Prabhat Nigam Says:

    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

  15. Exchange 2016: Http to Https Redirection « MSExchangeGuru.com Says:

    […] These are very much same steps, we had explained for Exchange 2013 – http://msexchangeguru.com/2013/10/30/http-redirect-owa-ecp/ […]

  16. Daniel Says:

    You are my hero. Finally I can use my ecp again. 🙂

Leave a Reply

migrate exchange to office 365

Categories

Archives