Curl filled a big missing hole. How can we code on plain text an HTTP Request in a reproducible and predictable way? The HTTP Protocol describe the request cont

Curl filled a big missing hole. How can we code on plain text an HTTP Request in a reproducible and predictable way? The HTTP Protocol describe the request content (method, headers, body...) but do not specify how the call is done (real IP address, port, certificates, timeout, etc.). Curl filled this and I think now it's options are the de-facto standard for describe in text an HTTP Request.