How are you using the URL? If you type it into your browser's address bar, then the browser will send a GET request to the server, which will always cause OWA 2007 to redirect to /owa . The only time it will not redirect is if you send a proper WebDAV verb such as PROPFIND, etc.
_____________________________
Lee. ___________________________________
Outlook Web Access for PDA and WAP: www.leederbyshire.com ___________________________________
Where is the changed URL coming from? Are you saying that when you type the /exchange/ URL into your browser, OWA itself is redirecting you to the /owa/ URL? Or do you have some sort of application doing it for you?
_____________________________
Lee. ___________________________________
Outlook Web Access for PDA and WAP: www.leederbyshire.com ___________________________________
Hm. I've never seen it produce a redirect URL with anything after the /owa/ . I've no idea where the %8%F9 (and everything after it) comes from. I assume that if you go to http://server/exchange , you simply get redirected to /owa/ ?
That's clearly wrong - although I've no idea where those extra characters are coming from. Have a look at the properties of the OWA Virtual Directory in the Exchange Management Console, and see if a value has been configured for its FQDN. There may be something strange in there.
Thanks, there was indeed some configuration issue that our System Administrator was able to fix. The URL no longer have "g1%85%F9"and for a https://myserver/exchange it now redirects properly to https://myserver/owa.
My original issue still remains though, a URL that points to a message still isn't redirecting properly.
To be honest, I wouldn't even expect it to have supplied anything like a complete URL, let alone one that almost works. The only thing that is missing is the last parameter &ae=item ?
Exception Exception type: System.ArgumentException Exception message: The ID is not a folder ID. ID = RgAAAAAH0T7pVYypSp4EMOpf4q/aBwBI46Z0ZyabTJ0PxnU1pTBcAAAAABRlAABI46Z0ZyabTJ0PxnU1pTBcAC+glKFUAAAA
Where do you get the document name exchange2007testemail.EML from? Is that just a guess that if the subject is simple, then the URL should be predictable? Or is there an application providing it for you?
So, you have an application that displays a WebDAV URL. You then copy/paste the URL into your browser. You then get redirected to /owa/ , but the display fails until you add an extra parameter to the URL and try again. Is that something like how it goes?
I have an application that looks up for the URL of an e-mail using WebDAV. When I use that URL on my Exchange 2007 server I get redirected to /owa/, but the URL doesn't work without an extra parameter.
I can change the application. That was my first approach. I've been trying to, but haven't been able to generate the ID that's on OWA URL. Exchange generates that ID only on redirect.
You could try getting the application to send its own GET request to the URL. The requesting object (WinHTTPRequest ?) will probably be redirected to the /owa/ URL. You can inspect the objects new location, split the string up to get the ID, and then construct a URL that should work okay.