Hi, With you suggestion won't I end up with all the URL's that don't require authorization in the db twice? Once with each server name.
How about if I index first the insecure server then the secure server with a a server alias? So if it finds the file already exists in the db under another name it will not reread it? Thanks, /Carl >Subject: Re: [htdig] multiple servers 1 authen 1 not >Mime-Version: 1.0 (Apple Message framework v481) >Cc: [EMAIL PROTECTED] >To: Carl Edwards <[EMAIL PROTECTED]> >From: Geoff Hutchison <[EMAIL PROTECTED]> >Content-Transfer-Encoding: 7bit >X-BeenThere: [EMAIL PROTECTED] >X-Mailman-Version: 2.0.9-sf.net >List-Help: <mailto:[EMAIL PROTECTED]?subject=help> >List-Post: <mailto:[EMAIL PROTECTED]> >List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/htdig-general>, <mailto:[EMAIL PROTECTED]?subject=subscribe> >List-Id: A mailing list for general ht://Dig discussion <htdig-general.lists.sourceforge.net> >List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/htdig-general>, <mailto:[EMAIL PROTECTED]?subject=unsubscribe> >List-Archive: <http://www.geocrawler.com/redir-sf.php3?list=htdig-general> >X-Original-Date: Sun, 19 May 2002 20:29:20 -0500 >Date: Sun, 19 May 2002 20:29:20 -0500 >X-DCC-vtss-Metrics: mx1.vitesse.com 1018; Body=1 Fuz1=1 Fuz2=1 > >> What I would really like is to have both servers >> in the start_url list and if a requires authentication >> response is received from the request then authenticate >> and save that servers name in the db. > >If you enter both servers in the start_url, it will index both. You >can't do quite what you want, since an authentication will be sent >regardless of whether it's asked. (This doesn't make much difference >since the non-authenticating server will just ignore that header.) > >So what I'd suggest is something like this: > >start_url: http://server1.foo.com/ http://secure1.foo.com/ >authentication: ... >local_urls: http://server1.foo.com/=/path/to/files/ \ > http://secure1.foo.com/=/path/to/files/ > >Since each document has one URL and only one URL, you'll need to index >"twice." Of course since you're indexing on the filesystem and your OS >will cache files, indexing should be relatively quick. > >-- >-Geoff Hutchison >Williams Students Online >http://wso.williams.edu/ > > >_______________________________________________________________ >Hundreds of nodes, one monster rendering program. >Now that's a super model! Visit http://clustering.foundries.sf.net/ > >_______________________________________________ >htdig-general mailing list <[EMAIL PROTECTED]> >To unsubscribe, send a message to <[EMAIL PROTECTED]> with a subject of unsubscribe >FAQ: http://htdig.sourceforge.net/FAQ.html > -Carl Edwards Design Automation _______________________________________________________________ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm _______________________________________________ htdig-general mailing list <[EMAIL PROTECTED]> To unsubscribe, send a message to <[EMAIL PROTECTED]> with a subject of unsubscribe FAQ: http://htdig.sourceforge.net/FAQ.html
