>>> This is a single setting (CURLOPT_DOH_URL) that when set will make
>>> libcurl use that service
>
>> Can a user select if the GET or POST method be used?
>
>Not yet. I just made it do POST since that's slightly easier (no base64url
>encoding). You think there's a good reason to offer the user to select which
>method to use?

Not a strong reason but GET is safe, idempotent and cacheable, in case that means anything in DoH. I could hypothetically see how it might be easier to build retry behaviour around GET, compared to POST.

Coding GET may also help build appreciation of how HTTP/2 Server Push and DoH might work (POST is banned in Server Push because it has a request body [1]).

Neither of these are core to the exciting capabilities of DoH.

Lucas

[1] https://tools.ietf.org/html/rfc7540#section-8.2

-----------------------------
http://www.bbc.co.uk
This e-mail (and any attachments) is confidential and
may contain personal views which are not the views of the BBC unless specifically stated.
If you have received it in
error, please delete it from your system.
Do not use, copy or disclose the
information in any way nor act in reliance on it and notify the sender
immediately.
Please note that the BBC monitors e-mails
sent or received.
Further communication will signify your consent to
this.
-----------------------------

-------------------------------------------------------------------
Unsubscribe: https://cool.haxx.se/list/listinfo/curl-library
Etiquette: https://curl.haxx.se/mail/etiquette.html
Received on 2018-06-18