Keep Server Online
If you find the Apache Lounge, the downloads and overall help useful, please express your satisfaction with a donation.
or
A donation makes a contribution towards the costs, the time and effort that's going in this site and building.
Thank You! Steffen
Your donations will help to keep this site alive and well, and continuing building binaries. Apache Lounge is not sponsored.
| |
|
 Topic: Reverse proxy with Blackberry Internet Service |
|
| Author |
|
ImRaptor
Joined: 07 Jul 2010
Posts: 3
Location: Saskatchewan
|
 Posted: Wed 07 Jul '10 17:41 Post subject: Reverse proxy with Blackberry Internet Service |
 |
|
I'm looking for some guidance to get my reverse proxy working with the BIS email push service.
The reverse proxy is working no problem with a Wing file server and OWA system, but for some reason when trying to connect with the BIS system it does not go through.
I had originally been hitting a dead spot when hitting the PROPFIND command submitted, but found what I needed to add to the httpd.conf to get the command passed through.
Now I am hitting a 403 error being returned from the OWA server regardless of what is connecting, BIS or just user via webmail.
I think my problem lies in this chunk here, but am not sure as I don't understand exactly what the code here is doing.
| Code: | ProxyPass /owa/ https://exch2009.internal/owa/
ProxyPassReverse /owa/ https://exch2009.internal/owa/
<Location /owa/ >
ProxyPassReverse /owa/
<LimitExcept GET PROPFIND OPTIONS REPORT>
Order deny,allow
Deny from all
</LimitExcept>
</Location> |
The line I am suspecting is the LimitExcept part, but have not figured enough out to be sure.
Any suggestions would be greatly appreciated, and some education to the LimitExcept modifier would be awesome. |
|
| Back to top |
|
ImRaptor
Joined: 07 Jul 2010
Posts: 3
Location: Saskatchewan
|
| Posted: Wed 07 Jul '10 17:51 Post subject: |
|
|
All of 30 seconds and I saw my first mistake.
Added POST to the LimitExcept line and corrected the 403 forbidden error.
However, I seem to be back to square one again with the BIS server not coming through.
Looking at the access log I am at a bit of a loss as it seems to be at the PROPFIND not implemented again, but after it already passes one...? Although the first run through had an error in itself.
| Code: |
67.223.91.21 - - [07/Jul/2010:09:43:26 -0600] "PROPFIND /owa/jharmon HTTP/1.1" 440 43
67.223.91.21 - - [07/Jul/2010:09:43:26 -0600] "GET /owa/ HTTP/1.1" 302 -
67.223.91.21 - - [07/Jul/2010:09:43:27 -0600] "GET /owa/auth/logon.aspx?url=https://exch2009.internal/owa/&reason=0 HTTP/1.1" 200 8359
67.223.91.21 - - [07/Jul/2010:09:43:28 -0600] "POST /owa/auth/owaauth.dll HTTP/1.1" 302 -
67.223.91.21 - - [07/Jul/2010:09:43:29 -0600] "GET /owa/ HTTP/1.1" 200 29760
67.223.91.21 - - [07/Jul/2010:09:43:30 -0600] "PROPFIND /owa/jharmon/ HTTP/1.1" 501 - |
|
|
| Back to top |
|
ImRaptor
Joined: 07 Jul 2010
Posts: 3
Location: Saskatchewan
|
| Posted: Wed 07 Jul '10 22:16 Post subject: |
|
|
A bit more info:
It appears that the underlying problem is actually the passing to the EWS directory, and not so much the OWA directory. Logging in via https to OWA works no problem. Trying the same with EWS not so much.
Going direct, ie bypassing the reverse proxy, I can connect to the EWS directory no problem.
So I know the problem is lying in the EWS configuration, which matches the OWA configuration posted above, but with the appropriate folder name changes. |
|
| Back to top |
|
|
|
|
|
|
