• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 615
  • Last Modified:

OWA and Apache Proxy

I can't seem to get OWA to load completely using Apache proxy, IIS, Exchange 2003, and Wins2k3.

Basic setup:

Linux 8.0, Apache 2.0.40, openssl

I've created my own certs. and setup the Linux box in my DMZ.  SSL seems to be working fine.

Exchange 2003, OWA, Wins2k3

Exchange is running on the trusted LAN and being proxied by the apache server.

SSL.conf (Proxy Portion)

<VirtualHost ip-address-of apache server:443>

DocumentRoot "/var/www/html"
ServerName FQDN of apache server:443
ErrorLog logs/ssl_error_log
TransferLog logs/ssl_access_log

RequestHeader set Front-End-Https "On"

ProxyRequests Off
ProxyPreserveHost On
ProxyVia On

ProxyPass / http://ip-address-of OWA server/exchange
ProxyPassReverse /http://ip-address-of OWA server/exchange
ProxyPass / http://ip-address-of OWA server/exchweb
ProxyPassReverse /http://ip-address-of OWA server/exchweb
ProxyPass / http://ip-address-of OWA server/public
ProxyPassReverse /http://ip-address-of OWA server/public
ProxyPass / http://ip-address-of OWA server/iisadmpwd
ProxyPassReverse /http://ip-address-of OWA server/iisadmpwd

Using the above configuration, I type https://apache-server-name.domain-name and establish a secure connection via the apache server.

I get a login screen and enter my username and password.
OWA loads but only displays the outer frames (preview panes) of the application. Where the graphics and messages should be I get the "http 404 file or directory not found" message.  OWA works correctly from the LAN connecting directly to the Exchange server: //servername/exchange/  but I can't get it to work from the outside/going through the proxy.  When I right click and select properties on the page displaying the 404 error it says it's looking for https://apache-server-name.domain-name /exchange/postmaster/Inbox/?Cmd=contents

I appreciate any ideas??

Thanks
0
wcuz
Asked:
wcuz
  • 2
  • 2
1 Solution
 
wcuzAuthor Commented:
Anyone have an idea on this??  Do I need to provide more detail?

Thanks.....
0
 
LeeDerbyshireCommented:
I don't know much about Apache, but here goes...

You say that you are expecting to access OWA using https://apache-server-name.domain-name . Normally, you would need /exchange on the end of there, so that makes me think that you have redirected your Default Web Site on the Exchange server to OWA.  If that is the case, then you probably also need

ProxyPass / http://ip-address-of OWA server
ProxyPassReverse /http://ip-address-of OWA server

Also, you are using https, but I don't see that in your ProxyPass definitions.  Maybe you don't actually need to do that (like I say, Apache isn't something I know much about), but I thought I'd mention it.
0
 
wcuzAuthor Commented:
I solved this problem using another web resource.......  The problem ended up having to do with authentication and the way the proxypass directives were setup.  The eventual solution was to add an additional proxypass statement defining only the root directory level on the exchange server.  This allowed me to authenticate and then gave access to the required virtual directories.  I can't really see awarding points for this question as my solution didn't come from the answer provided.  Thanks for the help anyway and if points are necessary LeeDerbyshire gets them considering that was the only response....
0
 
LeeDerbyshireCommented:
Hi wcuz.  I think that's what I was trying to say, although this board made a mess of the text and turned it into hyperlinks.  I'd be interested to see what your ProxyPass statements were (and so would anyone that finds this thread in the future).  Anyway, don't worry about assigning points - I don't think anyone expects it if you're not 100% satisfied, and I was only guessing anyway.
0

Featured Post

Easily manage email signatures in Office 365

Managing email signatures in Office 365 can be a challenging task if you don't have the right tool. CodeTwo Email Signatures for Office 365 will help you implement a unified email signature look, no matter what email client is used by users. Test it for free!

  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now