On Thu, 15 Aug 2019, Mike Crowe wrote:
I'll have a dig into the unit test infrastructure to see if I can find a way
to add a test case for this. I'd previously assumed that the use of a proxy
would make creating a test case difficult.
I believe we can reproduce this problem with a modified test 168, by moving
the credentials into the URL. Probably worth creating a new test case from:
diff --git a/tests/data/test168 b/tests/data/test168
index 20e0b6d9c..787bd796f 100644
--- a/tests/data/test168
+++ b/tests/data/test168
@@ -62,11 +62,11 @@ crypto
</features>
<name>
HTTP with proxy-requiring-Digest to site-requiring-Digest
</name>
<command>
-http://data.from.server.requiring.digest.hohoho.com/168 --proxy
http://%HOSTIP:%HTTPPORT --proxy-user foo:bar --proxy-digest --digest --user
digest:alot
+http://digest:a...@data.from.server.requiring.digest.hohoho.com/168 --proxy
http://%HOSTIP:%HTTPPORT --proxy-user foo:bar --proxy-digest --digest
</command>
</client>
# Verify data after the test has been "shot"
<verify>
--
/ daniel.haxx.se | Get the best commercial curl support there is - from me
| 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.haxx.se/mail/etiquette.html
