Arno Garrels wrote:
> {code}
> procedure THttpCli.DoRequestSync(Rq : THttpRequest);
> [..]
> {* Jul 12, 2004
> WARNING: The component now doesn't consider 401 status
>as a fatal error (no exception is triggered). This
>required a change in the application code if it was us
RTT wrote:
> Why this fix has not been added?
AFAIR Francois wasn't convinced, if there are no side effects and
Francois doesn't refuse it explicitly I'll add it.
--
Arno Garrels
> The first one is not really important, even if completes the logic
> already taken by the ParseURL for URLs missi
Why this fix has not been added?
The first one is not really important, even if completes the logic
already taken by the ParseURL for URLs missing the protocol , but the
second change, used by the THttpCli when parsing redirection URLs, is
IMO mandatory, because URLs beginning with '//' are val
Most servers close connections after a short request timeout,
that may happen even after a request has been successfully sent.
Currently THttpCli doesn't handle this case properly, as there
is no error passed to OnRequestDone and THttpCli.DoRequestSync()
doesn't raise an exception which it should
Arno Garrels wrote:
> colin masters wrote:
>> I am creating the component at runtime, which seems to work well,
>> however is there a way to surpress the connection timeout message if
>> I can not connect to a web site as I do not wish to see it.
>
> What message do you mean? Do you call synchrono
This fix applied to the ExtractURLEncodedValue, unit OverbyteIcsHttpSrv
Jul 06, 2002 V1.05 Thomas Smyth fixed
ExtractURLEncodedValue which had problem with names
beginning with
same sequence of chars.
Needs to be applied to the GetCookieValue function too
