Reverse Proxy to connect to OWA

Topics: Developer Forum, User Forum
Jan 21, 2010 at 3:11 AM

Hi expert,

Thanks for viewing.

I need to connect to my Outlook Web Access (Exchange 2003) server which is behind a firewall.
I manage to do the reverse proxy to open the page but  I encountered a problem in the authentication for the OWA. I can see the login page but after keying the user name and password, the page does not redirect and there are no errors.

Below is the code that I write.
ProxyPass ^/(.*)$ http://exchange.test.com/$1

Besides, after the reverse proxy, the browser will update the address bar to the new location (which is http://exchange.test.com/exchange..). How can I prevent the addess url to be changed?

Kindly advise
Thanks in advance

Coordinator
Jan 21, 2010 at 10:20 PM

I don't know the answer to that.

If I were you I would get a debugging HTTP Proxy like Fiddler, and examine the HTTP Transactions going back and forth. 

That would get you started.

Coordinator
Mar 24, 2010 at 6:03 PM

Hello TheCross. Here's an update on this older discussion. I found a few problems in the implementation of ProxyPass:

  1. If the app tried to submit data larger than 48k across the proxy, the proxy would silently truncate the data. (workitem 25950)
  2. HTTP Headers were not being faithfully passed across the proxy. (workitem 26146)
  3. Chunked encoding, either on the POST or the reply, is not currently supported in IIRF. (workitem 25703)

With these problems in the v2.0 proxy implementation, I'm not surprised it didn't work for OWA.

I've made fixes to the first two issues. These are available in the latest update of IIRF v2.1 beta, v2.1.0.15, available at http://iirf.codeplex.com/releases/view/36814. I'd encourage everyone using ProxyPass to get that update.

I plan to fix the last item within the week.

Also, an additional hint: To check if you have correctly configured IIRF as an ISAPI extension, you can use your browser to visit a URL like: http://yourserver/INSERT ANYTHING HERE.iirf . This will cause a diagnostic page to be returned. It looks like this:

If you don't get that page, then you haven't configured IIRF properly.