From c111033595baaddf02fca866c99972fc962e2d9c Mon Sep 17 00:00:00 2001 From: Daniel Stenberg Date: Fri, 16 Feb 2001 13:41:34 +0000 Subject: [PATCH] removed --continue task (done) added URL to the NTLM task --- docs/TODO | 11 +++++------ 1 file changed, 5 insertions(+), 6 deletions(-) diff --git a/docs/TODO b/docs/TODO index e6a92a7..487aaee 100644 --- a/docs/TODO +++ b/docs/TODO @@ -23,11 +23,8 @@ For the future URLs mentioned in the list. I figure -O or something would have to be implied by such an action. - * Improve the regular progress meter with --continue is used. It should be - noticable when there's a resume going on. - * Add a command line option that allows the output file to get the same time - stamp as the remote file. We already are capable of fetching the remote + stamp as the remote file. libcurl already is capable of fetching the remote file's date. * Make the SSL layer option capable of using the Mozilla Security Services as @@ -58,13 +55,15 @@ For the future started in October 1999 but halted again since it proved more work than we thought. It is still a good idea to implement though. - * Authentication: NTLM. It would be cool to support that MS crap called NTLM + * Authentication: NTLM. It would be to support that MS crap called NTLM authentication. MS proxies and servers sometime require that. Since that protocol is a proprietary one, it involves reverse engineering and network sniffing. This should however be a library-based functionality. There are a few different efforts "out there" to make open source HTTP clients support this and it should be possible to take advantage of other people's hard - work. http://modntlm.sourceforge.net/ is one. + work. http://modntlm.sourceforge.net/ is one. There's a web page at + http://www.innovation.ch/java/ntlm.html that contains detailed reverse- + engineered info. * RFC2617 compliance, "Digest Access Authentication" A valid test page seem to exist at: -- 2.7.4