OWA on a unique port

[jmair]

I have IIS and Apache on the same server. for OWA only, i'm using IIS.
On a test server I changed the deafult webpage port on IIS to 81, then tested to see if i could get to either webserver using port 81 as the trigger.
for example OpenDNS would bring up a test file on the IIS server while OpenDNS would bring up a test file on the apache server. I was hoping I could use this direction to run OWA on IIS.

Results.
The login works, I get a login, then it directs me to a dead page.

I have taken down apache and changed the port back to 80 and OWA works fine.

Any thoughts on how I can get OWA to work this way?

ps, if you need any additional info let me know.

Thanks!

[Edu-IT]

Can you not force OWA to use SSL instead, port 443. Then I think that perhaps it might login? As long as Apache isn't set to use this port.

[mrcrazy04]

Doesn't OWA prefer SSL?
If so, and you're not using SSL on Apache, just force SSL for the directory, and make all shortcuts point to https://www.mysite.com/
There's free certificates and threads on where to get them.

Edit: Beaten to it! I agree with Edu-IT.

[Jay]

NB: If you can get OWA to work on a non standard port, you can use apache virtual directories/hosts to pass HTTP(S) for /OWA/ requests onwards to IIS. (AJP Proxy or similar module I think)

[jmair]

Worked like a charm. Thanks guys.