On Mon, 20 Nov 2023, Yifei Kong via curl-library wrote:
Thanks for all your suggestions. Another issue that bugs me is that it seems
that this option does not work with HTTP. The documentation says it only
works with FTP, IMAP, POP3, SMTP and SSH. Considering the wide usage of
HTTP, can we exp
Thanks for all your suggestions. Another issue that bugs me is that it
seems that this option does not work with HTTP. The documentation says it
only works with FTP, IMAP, POP3, SMTP and SSH. Considering the wide usage
of HTTP, can we expand the available protocols of it to more?
On Mon, Nov 20, 2
On 19-Nov-23 15:07, Ray Satiro via curl-library wrote:
On 11/19/2023 2:35 PM, Timothe Litt via curl-library wrote:
While I agree that a struct timespec* would be a better choice,
consistency in an API is important.
All the other _MS functions could also use a stuct timespec (you get
nanosec
On 11/19/2023 2:35 PM, Timothe Litt via curl-library wrote:
While I agree that a struct timespec* would be a better choice,
consistency in an API is important.
All the other _MS functions could also use a stuct timespec (you get
nanoseconds).
Perhaps a (CURLOPT_PRECISE_TIMEOUT, {CURLOPT_SE
On 19-Nov-23 13:01, Cristian Rodríguez via curl-library wrote:
On Sat, Nov 18, 2023 at 11:05 AM Daniel Stenberg via curl-library
wrote:
On Sat, 18 Nov 2023, Yifei Kong via curl-library wrote:
> However, there is only `CURLOPT_SERVER_RESPONSE_TIMEOUT` and no
> `CURLOPT_SERVER_R
On Sat, Nov 18, 2023 at 11:05 AM Daniel Stenberg via curl-library <
curl-library@lists.haxx.se> wrote:
> On Sat, 18 Nov 2023, Yifei Kong via curl-library wrote:
>
> > However, there is only `CURLOPT_SERVER_RESPONSE_TIMEOUT` and no
> > `CURLOPT_SERVER_RESPONSE_TIMEOUT_MS`, is it possible to add thi