Re: AW: [squid-users] Exchange WebServices

From: Amos Jeffries <squid3_at_treenet.co.nz>
Date: Wed, 07 Mar 2012 15:25:19 +1300

On 07.03.2012 11:50, Fuchs, Martin wrote:
> Hi, Amos !
>
> ...
>>ignore_expect_100 could be the reason. Exchange tries to use
>> Expect:100-continue feature sometimes. Your browser may be timing out
>> before it sends POST'd data.
>>Although that said, the above POST look to be part of an NTLM
>> handshake and only taking 150ms.
>
> Without ignore_expect_100 we get
>
> 1331073616.344 0 207.46.14.62 NONE/417 4157 POST
> https://g1.xxx.de/EWS/Exchange.asmx - NONE/- text/html
> 1331073616.886 0 207.46.14.62 NONE/417 4157 POST
> https://g1.xxx.de/EWS/Exchange.asmx - NONE/- text/html
> 1331073659.207 0 207.46.14.62 NONE/417 4157 POST
> https://g1.xxx.de/EWS/Exchange.asmx - NONE/- text/html
>
> But how can I find out what might go wrong ?

What could go wrong with ignore_expect_100 OFF is the client displays
an error page instead of retrying with HTTP/1.0 format request like it
is supposed to.

What could go wrong with ignore_expect_100 ON is the client waiting an
annoyingly long timeout before anything happens. Exactly the behaviour
you noticed earlier.

Amos
Received on Wed Mar 07 2012 - 02:25:25 MST

This archive was generated by hypermail 2.2.0 : Wed Mar 07 2012 - 12:00:02 MST