From 26febe076913aabc3923f7871a3578666400432f Mon Sep 17 00:00:00 2001
From: yhirose <yuji.hirose.bug@gmail.com>
Date: Fri, 16 Oct 2026 23:52:15 -0400
Subject: [PATCH] Say why the Digest uri is in origin form

Through a plain-HTTP proxy the request line carries the absolute form,
while the Digest uri stays in origin form, as curl sends it. The comment
cited RFC 7616 3.4, which asks for the effective request URI.
---
 httplib.h | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/httplib.h b/httplib.h
index 933e4265..9f911a01 100644
--- a/httplib.h
+++ b/httplib.h
@@ -10888,7 +10888,8 @@ inline bool process_client_socket_ssl(
   return callback(strm);
 }
 
-// `uri` is req's request-target in origin form (RFC 7616 3.4).
+// `uri` is req's request-target in origin form, as curl sends it, also when
+// the request line carries the absolute form for a proxy.
 inline std::pair<std::string, std::string> make_digest_authentication_header(
     const Request &req, const std::string &uri,
     const std::map<std::string, std::string> &auth, size_t cnonce_count,