|
I just got this
email from a Microsoft tech. Does this help at all? I think I might have
a hunch at what could be going on………… When you sync
against a mailbox that resides in the same site as the publicly accessible CAS
server the request header sent between the device and the CAS server looks like
this: RequestHeader : POST
/Microsoft-Server-ActiveSync/default.eas?Cmd=FolderSync&DeviceId=BAD73E6E02156460E800185977C03182&DeviceType=PocketPC Cache-Control:
no-cache Connection: Keep-Alive Content-Length: 13 Content-Type:
application/vnd.ms-sync.wbxml Accept-Language: en-us Authorization:
******** Host:
mail.thesimpsons.com Reverse-Via: HANKRRAS MS-ASProtocolVersion:
12.1 X-MS-PolicyKey: 0 When you sync
against a mailbox that resides in the another site, and the publicly accessible
CAS server has to proxy the request to another CAS, the request header sent
between the device and the CAS server looks like this: RequestHeader : POST
/Microsoft-Server-ActiveSync/default.eas?Cmd=Provision&DeviceId=BAD73E6E02156460E800185977C03182&DeviceType=PocketPC Cache-Control:
no-cache Content-Length: 41 Content-Type:
application/vnd.ms-sync.wbxml Accept-Language: en-us Authorization:
******** Expect: 100-continue Host:
hank1.simpsons.com Referer:
https://mail.thesimpsons.com/Microsoft-Server-ActiveSync/default.eas?Cmd=Provision&DeviceId=BAD73E6E02156460E800185977C03182&DeviceType=PocketPC X-ExCompId:
AirSync Reverse-Via: HANKRRAS MS-ASProtocolVersion:
12.1 X-MS-PolicyKey: 0 X-EAS-Proxy:
S-1-5-21-1937965725-1210898722-3484717379-1130,simpsons\moe Notice the three
extra HTTP verbs (highlighted) that get added to the proxy request header. My
hunch is that when APACHE receives this header it doesn’t understand
those extra verbs and the request fails. I have found some similar issues when
customers were using ISA 2000 to reverse publish their servers and there was an
update to ISA that added verbs to the product so it could understand the
request. Can you talk to the APACHE admin and see if he can confirm if APACHE
is having trouble processing these extra verbs, and if so, is there anyway to
get APACHE to deal with those verbs going forward. This might explain why it
all works internally (as nothing is inspecting or processing those extra verbs)
but fails when going through APACHE. From: Dwyer, Simon
[mailto:sdwyer@xxxxxxxxxxxxx] Hi all, Having an issue with Activesync and exchange 2007 going
through mod_proxy. It works fine when the mail box belongs to the internet
accessible CAS but when that CAS passes the request to another CAS it fails
with a 0x85010014 error on the activesync device. This works fine if the mobile device is on the internal
network bypassing the proxy. So I am kinda stuck. Config follows, so
could someone see if anything is jumping out at them as wrong: <VirtualHost 10.10.10.100:443> DocumentRoot "/opt/www/owa" ServerName <domain>:443 ServerAdmin DirectoryIndex index.html index.php SSLEngine on SSLCipherSuite
ALL:!ADH:!EXPORT56:RC4+RSA:+HIGH:+MEDIUM:+LOW:+SSLv2:+EXP:+eNULL SSLCertificateFile <Cert Key> SSLCertificateKeyFile <cert key> SSLCertificateChainFile <cert key> SSLProxyEngine on RewriteEngine On KeepAlive On MaxKeepAliveRequests 200 KeepAliveTimeout 600 RequestHeader set Front-End-Https "On" ProxyRequests Off ProxyPreserveHost On ProxyVia full <Proxy *> Order deny,allow Allow from all </Proxy> ProxyPass
/Microsoft-Server-ActiveSync/
https://<internalserver>/Microsoft-Server-ActiveSync/ smax=50 max=60
ttl=1000 timeout=1000 ProxyPassReverse /Microsoft-Server-ActiveSync/
https://<Domain>/Microsoft-Server-ActiveSync/ ProxyPass /
https://<internalServer>/ ProxyPassReverse / https//<Domain>/ </VirtualHost> |
|