The setup is as follows

Windows Server 2012 R2 running Exchange 2013 CU5 - CAS Role
Windows Server 2012 R2 Running Exchange 2013 CU5 - Mailbox Role
Published via Web Application Proxy, using ADFS on Server 2012 R2

The problem

Browse to https://webmail.contoso.com/owa - log into OWA as myself this works fine - try and open another users mailbox that i have full access to, i get HTTP 400 bad request

If i browse to https://servername and perform the same procedure it works.   This leave me to the conclusion that the Web Application Proxy server / ADFS server is at fault

this KB article is not relevant in this instance, as I can resolve the names correctly; http://support.microsoft.com/kb/2770796/en-au

Any suggestions

Thank you.

• Edited by mr_burgess Thursday, June 19, 2014 12:17 AM additonal info

Hi,

Does the issue happen to all users who want to access a shared mailbox in OWA?

Please create a test mailbox and assign full access permission for a user. Then access the shared mailbox by using Open Another Mailbox in OWA to have a try. If the issue happens to all shared mailboxes, please collect any error logs for further anylysis.

Thanks,

Hi

thanks for the reply - i have tried other mailbox's and have logged on as other accounts, all still get the same error

with regards to logs, what logs would you be interesting in seeing ?

thank you.

Same issue here.  In my case I have a NetScaler behind the WAP server.  Performing the same test on either the Exchange server(s) directly or via the NetScaler works fine.  Only when using the WAP server do you get the HTTP 400 error when opening additional mailboxes.

Have you had any luck with this?

Cheers

I can reproduce. Exchange 2010 SP3 on Windows Server 2008 R2 SP1. WAP on 2012 R2 (obviously, I guess :-)

Happens whenever OWA is accessed through WAP, for all users. In my environment the internal and external URLs are the same.

I tried setting DisableTranslateUrlInRequestHeaders and DisableTranslateUrlInResponseHeaders in the WAP publishing rule, just in case it was the way it was translating the @ in the URL, but no luck there.

At a guess, I'm going to say the @ is the problem.

Https://owa.mydomain.com/owa/ works fine thru WAP, https://owa.mydomain.com/owa/AnotherUser@mydomain.com breaks.

Hi, we have same problems but with this configuration:

Windows Server 2008 R2 running Exchange 2010 SP3 CU7 - CAS Role
Windows Server 2008 R2 Running Exchange 2010 SP3 CU7 - Mailbox Role
Published via Web Application Proxy 3.0, using Pass through on Server 2012 R2

The problem

Browse to INTERNET https://webmail.contoso.com/owa - log into OWA as myself this works fine - try and open another users mailbox that i have full access https://webmail.contoso.com/name.surname@contoso.com , I get HTTP 400 bad request

If I browse to https://servername.local/owa  and perform the same procedure it works.  

Probably the problem is @ caracter in translation from outside to inside.

IIS Server give only this WARNING :(

Other people have same problem.

The problem isn't the shared forder that is open from the owa box, because internally (INTRANET) all work fine.

Probably is the "translation of the URL with "@" https://webmail.contoso.com/name.surname@contoso.com that have problems in WAP 3.0

I have tried many combination of authentication (Basic, NTLM, Kerberos) on CAS (set-owa)

and setting on WAP Set-WebApplicationProxyApplication -ID A9D81AC7-9C3D-7CF9-C15E-xxxxxxxx -DisableTranslateUrlInRequestHeaders -DisableTranslateUrlInResponseHeaders

but no solutions.

Aurelio

• Edited by sistemisti5t Thursday, November 13, 2014 12:38 AM

You should contact microsoft support for a hotfix, we had this issue it's caused by the server 2012 r2 wap, the hotfix fixes how the entries for the url are being interpreted when you switch from your own mailbox to open someone elses mailbox. 

The hotfix is still in testing phase, so actually not advised to use it in production, although we have it running without issue for several months, will keep it installed untill there's an official hotfix available.

Thanks,

we hope that the official hotfix will be avaiable as soon as possible

Aurelio

I'm not in the office at the moment, but quickly looking at the email with the download link, it's referred to as:

KB Article Number(s): 2530309

437467_intl_x64_zip.exe

Also last update from microsoft is that they are finishing testing and are aiming for a february-march release date.

• Edited by DannySan Friday, January 30, 2015 10:06 AM

You should contact microsoft support for a hotfix, we had this issue it's caused by the server 2012 r2 wap, the hotfix fixes how the entries for the url are being interpreted when you switch from your own mailbox to open someone elses mailbox. 

The hotfix is still in testing phase, so actually not advised to use it in production, although we have it running without issue for several months, will keep it installed untill there's an official hotfix available.

Hi do you have NEWS about the HOTFIX?

Thanks

Aurelio

There is Application Proxy Blog page with list of recommended hotfixes including this one.

http://blogs.technet.com/b/applicationproxyblog/archive/2015/03/04/web-application-proxy-updates-for-windows-server-2012-r2.aspx

HI,

I have installed the hotfix NOW

3042127 "HTTP 400 - Bad Request" error when you open a shared mailbox through WAP in Windows Server 2012 R2

After reboot all works FINE!!!

Problem solved!

THANKS

Aurelio