RE: [squid-users] Regarding long pauses with Squid3 as a reverse proxy to Exchange 2010 OWA

Amos
Thanks.

I had come across references to the check for chunked vs Chunked in one of
the release notes for a more recent squid. I suspect this is the problem
given the iPhone is issuing "Chunked" rather than "chunked" as the value for
the Transfer-Encoding attribute.

I will try and re-compile the version of squid I have (3.0 stable 19) with
the "caseless" comparison from 3.1.7 and see what happens.

Thank you again.

Regards

Paul

-----Original Message-----
From: Amos Jeffries [mailto:squid3_at_treenet.co.nz]
Sent: Monday, 30 August 2010 1:57 PM
To: squid-users_at_squid-cache.org
Subject: RE: [squid-users] Regarding long pauses with Squid3 as a reverse
proxy to Exchange 2010 OWA

On Mon, 30 Aug 2010 12:51:27 +1000, "Paul Freeman"
<paul.freeman_at_eml.com.au> wrote:
> Amos
> I suspect I may have come across another situation related to chunked
> Transfer-Encoding although I am not sure yet.
>
> I have verified that using a HTC Desire I can successfully sync email,
> calendar and notes including sending new calendar items and new email
and
> replies to emails.
>
> However, when I try this using an iPhone (3GS, running IOS 4.0.1) it
cannot
> send email. Pulling data (calendar, email) from Exchange works OK
though.
>
> Squid is replying with a 501 error. I have increased debugging on the
> squid
> reverse proxy and notice the iPhone is sending a post request, which I
have
> included below (certain private values replaced), which Squid does not
> like.
>
> POST
>
/Microsoft-Server-ActiveSync?User=username&DeviceId=fjsdlfjlsdjflskj&DeviceTy
> pe=iPhone&Cmd=SmartReply HTTP/1.1
> Host: external.server.name
> Content-Type: application/vnd.ms-sync.wbxml
> Ms-Asprotocolversion: 14.0
> User-Agent: Apple-iPhone2C1/801.306
> X-Ms-Policykey: 4281201554
> Authorization: Basic asjlfjdal;sjdfl;ajsdf;lajsl;f
> Accept: */*
> Accept-Language: en-us
> Accept-Encoding: gzip, deflate
> Connection: keep-alive
> Transfer-Encoding: Chunked
>
> What causes Squid to issue a 501 reply? Is it related to
> Transfer-Encoding?

It's emitted on OPTIONS requests, unidentified transfer-encodings, and URL
which are unknown or invalid protocols for the method given.

The above POST might be 501 rejected if it was received by Squid as a
non-transparent or non-reverse-proxy request.

Or if the squid version was older than 3.1.5. Which only accept "chunked"
as implied by the RFC texts. Newer releases are supposed to be more lenient
and accept encoding names case-less.

Amos
 

__________ Information from ESET Smart Security, version of virus signature
database 5407 (20100829) __________

The message was checked by ESET Smart Security.

http://www.eset.com
 
 

__________ Information from ESET Smart Security, version of virus signature
database 5407 (20100829) __________

The message was checked by ESET Smart Security.

http://www.eset.com
 
Received on Mon Aug 30 2010 - 05:05:27 MDT