- From: Sébastien Barnoud <sebastien.barnoud@prologism.fr>
- Date: Wed, 4 Jun 2014 20:43:38 +0200
- To: Daniel Stenberg <daniel@haxx.se>
- Cc: Willy Tarreau <w@1wt.eu>, Michael Sweet <msweet@apple.com>, "William Chan (?????????)" <willchan@chromium.org>, HTTP Working Group <ietf-http-wg@w3.org>, Matt Menke <mmenke@chromium.org>
But i have made a custom version if curl and GSoap to handle that. > Le 4 juin 2014 à 20:14, Daniel Stenberg <daniel@haxx.se> a écrit : > >> On Wed, 4 Jun 2014, Sébastien Barnoud wrote: >> >> I have several years ago used customized Curl and GSoap to automaticaly retry requests on such a condition. As this is used for money transfer, it is very important to distinguish retryable errors (connect timeout, ...) from others errors (request timeout, ...). On a close, no retry is possible except if the server replies with this 408. So i agree with you, and i know that some application uses this feature. > > But then, curl doesn't read from the connection until after it has sent its request (or part of request) so the "problematic" case with getting a response before even sending a request will never be noticed. > > -- > > / daniel.haxx.se
Received on Wednesday, 4 June 2014 18:44:06 UTC