Buy commercial curl support from WolfSSL. We help you work
out your issues, debug your libcurl applications, use the API, port to new
platforms, add new features and more. With a team lead by the curl founder
himself.
Re: Feature request: extend CURLOPT_RESOLVE to allow adding non-permanent DNS cache entries
- Contemporary messages sorted: [ by date ] [ by thread ] [ by subject ] [ by author ] [ by messages with attachments ]
From: Daniel Stenberg via curl-library <curl-library_at_cool.haxx.se>
Date: Wed, 18 Nov 2020 15:00:20 +0100 (CET)
On Wed, 18 Nov 2020, Groke, Paul via curl-library wrote:
> I want to propose to add a feature by which libcurl users can pre-populate
> DNS cache entries that will expire just like those added by libcurl itself.
> I would suggest adding an additional recognized prefix for the
> CURLOPT_RESOLVE strings. Maybe a '?' or '+'.
I think it's a fair suggestion!
Exactly how to extend the format can of course be further discussed. I think I
would prefer a slighly more descriptive text, like perhaps ":temp" - and we
could then introduce that extra field for further instructions if we want to
later on.
Go for it!
> Another idea would be to allow the user to specify an explicit TTL.
If we don't have a user for such a feature now, then let's save it for later.
We should just make sure that we don't shut the door for doing it in the
future.
Date: Wed, 18 Nov 2020 15:00:20 +0100 (CET)
On Wed, 18 Nov 2020, Groke, Paul via curl-library wrote:
> I want to propose to add a feature by which libcurl users can pre-populate
> DNS cache entries that will expire just like those added by libcurl itself.
> I would suggest adding an additional recognized prefix for the
> CURLOPT_RESOLVE strings. Maybe a '?' or '+'.
I think it's a fair suggestion!
Exactly how to extend the format can of course be further discussed. I think I
would prefer a slighly more descriptive text, like perhaps ":temp" - and we
could then introduce that extra field for further instructions if we want to
later on.
Go for it!
> Another idea would be to allow the user to specify an explicit TTL.
If we don't have a user for such a feature now, then let's save it for later.
We should just make sure that we don't shut the door for doing it in the
future.
-- / daniel.haxx.se | Commercial curl support up to 24x7 is available! | Private help, bug fixes, support, ports, new features | https://www.wolfssl.com/contact/ ------------------------------------------------------------------- Unsubscribe: https://cool.haxx.se/list/listinfo/curl-library Etiquette: https://curl.se/mail/etiquette.htmlReceived on 2020-11-18