I've mentioned this before, but maybe it's time to bring it up again: I've implemented a Common HTTPClient-based HTTP fetcher, mostly for the NTLM authentication, using code from Andy Hedges as a start.
Is there any consensus whether moving to the Commons HTTPClient (vs. Sun's java.net.URL) is a good or bad idea? The only thing missing right now from my code is the part that reads several sites' IDs and passwords from the config files. Ken On Sat, 26 Mar 2005 16:06:22 +0100 (CET), Stefan Grroschupf (JIRA) <[EMAIL PROTECTED]> wrote: > New Http Authentication mechanism > --------------------------------- > > Key: NUTCH-26 > URL: http://issues.apache.org/jira/browse/NUTCH-26 > Project: Nutch > Type: Improvement > Components: fetcher > Reporter: Stefan Grroschupf > Priority: Trivial > > transferred from: > http://sourceforge.net/tracker/index.php?func=detail&aid=990560&group_id=59548&atid=491356 > submitted by: > Matt > > Here's a patch and lib (commons-codec used for Base64 > encoding) which implements hasic http authentication. > I've attempted to build it so we can add more > authentication methods at a later time. > > This also includes the previously discussed > MultiProperties class which allows multiple headers with > the same name (as opposed to Properties which allows > only a single). > > I believe both John and Doug have had some comments > on this. > > Matt > > -- > This message is automatically generated by JIRA. > - > If you think it was sent incorrectly contact one of the administrators: > http://issues.apache.org/jira/secure/Administrators.jspa > - > If you want more information on JIRA, or have a bug to report see: > http://www.atlassian.com/software/jira > > -- Absolute power corrupts absolutely, but model train sets do a pretty good job as well -- 2/28/05, in a odd dream
