[prev in list] [next in list] [prev in thread] [next in thread] 

List:       squid-users
Subject:    Re: [squid-users] Exchange ActiveSync and squid reverse proxy
From:       Amos Jeffries <squid3 () treenet ! co ! nz>
Date:       2008-11-28 2:53:30
Message-ID: 492F5D2A.5050609 () treenet ! co ! nz
[Download RAW message or body]

Koopmann, Jan-Peter wrote:
> Hi,
> 
> we are using squid as reverse proxy for Outlook RPC over HTTPS without
> any problems. Today some iPhone users/customers wanted to use Exchange
> ActiveSync as well so I decided to "simply" allow
> /Microsoft-Server-ActiveSync/* as well and hoped all is well. Far from
> it. The Exchange ActiveSync account on the iPhone can be setup without
> problems and verifies. Sending E-Mails is no problem. However receiving
> e-mails and e-mail push does not work at all. Whenever the user tries to
> receive mails I see this in cache.log:
> 
> 2008/11/25 11:28:26| The request OPTIONS
> https://outlook.test.de:443/Microsoft-Server-ActiveSync is ALLOWED,
> because it matched 'url_allow'
> 2008/11/25 11:28:26| The reply for OPTIONS
> https://outlook.test.de/Microsoft-Server-ActiveSync is ALLOWED, because
> it matched 'all'
> 2008/11/25 11:28:26| Invalid chunk header '
> '
> 2008/11/25 11:28:26| clientWriteComplete: Object aborted
> 2008/11/25 11:28:27| The request POST
> https://outlook.test.de:443/Microsoft-Server-ActiveSync?User=testuser&De
> viceId=Appl88843DYCY7H&DeviceType=iPhone&Cmd=FolderSync is ALLOWED,
> because it matched 'url_allow'
> 2008/11/25 11:28:27| clientReadBody: start fd=12 body_size=13
> in.offset=13 cb=0x8088430 req=0x888c000
> 2008/11/25 11:28:27| clientProcessBody: start fd=12 body_size=13
> in.offset=13 cb=0x8088430 req=0x888c000
> 2008/11/25 11:28:27| clientProcessBody: end fd=12 size=13 body_size=0
> in.offset=0 cb=0x8088430 req=0x888c000
> 2008/11/25 11:28:27| The reply for POST
> https://outlook.test.de/Microsoft-Server-ActiveSync?User=testuser&Device
> Id=Appl88843DYCY7H&DeviceType=iPhone&Cmd=FolderSync is ALLOWED, because
> it matched 'all'
> 2008/11/25 11:28:27| Invalid chunk header '
> '
> 2008/11/25 11:28:27| clientWriteComplete: Object aborted
> 
> This seems to be the root of the problem but how do I fix it if I can
> fix it at all? Customer is running squid-2.7.4 against Exchange 2003.
> 
> 
> Any help greatly appreciated.
> 
> Regards,
>   JP

Appears to be squid not handling a chunked-encoding situation properly.
Please report this as a bug.

If you intended to have Squid simulating a HTTP/1.1 service you have 
problems. Otherwise you can use the Accept-Encoding workaround 
(basically deny the header to those requests).

Amos
-- 
Please be using
   Current Stable Squid 2.7.STABLE5 or 3.0.STABLE10
   Current Beta Squid 3.1.0.2
[prev in list] [next in list] [prev in thread] [next in thread]