Frans van Daalen wrote:
>>>> You are right, I did not test the GetAsync, in async mode
>>>> RequestDone is actually fired with StatusCode 0 after relocation.
>>>>
>>>> Triggered by a call to CheckDelaySetReady in GetBodyLineNext.
>>>
>>> When I add a check for FLocationFlag there it _SEEMS_ to fix it,
>>> has to be still tested very hard in order not to introduce new bugs:
>>>
>>> TriggerDocEnd;
>>> if {(FResponseVer = '1.0') or (FRequestVer = '1.0') or }
>>> { see above }
>>> { [rawbite 31.08.2004 Connection controll] }
>>> (FCloseReq) then { SAE 01/06/04 }
>>> FCtrlSocket.CloseDelayed
>>> else if not FLocationFlag then // <== Try this change and
>>> test, test, test...
>>> CheckDelaySetReady; { 09/26/08 ML }
>>>
>>
>> I tested it and it seems indeed to solve the problem. I spend several
>> hours extra trying to read and understand the reason behind this but
>> httprot file is not that easy to read :-)
>>
>> Well done and thank you!
>
> Update : Seems there are still scenario's where the problem returns
> also sometimes the proxy settings are lost creating a 407 when a
> relocation happens. Seems to happen when executing a GetAsync and a
> relocate is triggered (with follow relocation set)
Thanks for the report. That's probably because SetReady is skipped with
it's code related to proxy and www-authentication :(
The HTTP component is a TRUE beast.
--
Arno Garrels
--
To unsubscribe or change your settings for TWSocket mailing list
please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be
