[htdig] filtering returned url's

2001-01-23 Thread Dave Salisbury
I'd like to be able to preserve the user's state, held in the query string, when a search is done. So my idea is to return just the urls from a search that only match the state of the user. Basically, we have a ?lang=en or ?lang=fr, and since many of our pages are not translated yet, it's the

Re: [htdig] Spelling Help

2001-01-18 Thread Dave Salisbury
okay, here's one for the gurus. I'd like to be able to preserve user state, which is held in the query string. So my idea is to return just the urls from a search that match the state of the user. Basically, we have a ?lang=en or ?lang=fr, and since many of our pages are not translated yet,

Re: [htdig] 3.1.3 engine on 3.1.5 db

2001-01-11 Thread Dave Salisbury
Thanks for the reply.. If you created your database with htdig 3.1.5, and want to search it with htsearch 3.1.3, that's a bad idea. The most glaring bug in releases before 3.1.5 is in htsearch, so you really should upgrade it. I take it one of the worst things is the security hole which

[htdig] 3.1.5 engine on 3.1.3 db

2001-01-05 Thread Dave Salisbury
does anyone know if I can read the database created using 3.1.5 with a 3.1.3 engine? ( just hoping to perhaps save some time before setting things up ) I don't see anything in the release notes to indicate it can't be done. thanks for any info Dave To

Re: [htdig] 3.1.5 engine on 3.1.3 db

2001-01-05 Thread Dave Salisbury
Hutchison [EMAIL PROTECTED] To: Dave Salisbury [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Friday, January 05, 2001 1:14 PM Subject: Re: [htdig] 3.1.5 engine on 3.1.3 db On Fri, 5 Jan 2001, Dave Salisbury wrote: does anyone know if I can read the database created using 3.1.5 with a 3.

Re: [htdig] 3.1.5 engine on 3.1.3 db

2001-01-05 Thread Dave Salisbury
From: Geoff Hutchison [EMAIL PROTECTED] But the root question is: Why are you having problems compiling 3.1.5 on IRIX? I posted this a day or two ago, with no responses. Any help would be appreciated! IRIX 6.5 things go well until these errors show up. Dave make[1]: Entering directory

[htdig] compiling on IRIX64 6.5

2001-01-02 Thread Dave Salisbury
When compiling 3.1.5 on IRIX 6.5 I get bad things. I've tried a myriad of configur options and makefile changes but to no avail. Any help is appreciated! Dave - things are fine till this line: g++ -o htfuzzy -L../htlib -L../htcommon

[htdig] compiling on IRIX64 6.5

2001-01-02 Thread Dave Salisbury
addendum: I forgot to mention that after the warnings comes a long list of error messages. thanks Dave -- ld32: WARNING 131: Multiply defined weak symbol:(__tf6Object) in Endings.o and Synonym.o (2nd definition ignored). ld32: WARNING 131:

[htdig] query string

2000-12-20 Thread Dave Salisbury
I hope this hasn't been asked before. I'm new to htdig, and couldn't find an answer in the archives. using htdig 3.1.3 on an sgi, I'm finding that a query string of ?one=1two=2three=3 is stored as ?one=1=2=3 sort of like deciphering 's as html document character set characters, but replaced

Re: [htdig] Indexing Restricted Pages

2000-12-20 Thread Dave Salisbury
I'd imagine you might be able to do something along these lines: Directory require valid-user order allow, deny deny from all allow from .your.domain.com /Directory or some such permutation. Dave - Original Message - From: Douglas Kline [EMAIL PROTECTED] To: Geoff Hutchison [EMAIL

Re: [htdig] Indexing Restricted Pages

2000-12-20 Thread Dave Salisbury
Oh yea.. also add a "satisfy any" in the Directroy block. ta DS - Original Message - From: Douglas Kline [EMAIL PROTECTED] To: Geoff Hutchison [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Wednesday, December 20, 2000 4:39 PM Subject: Re: [htdig] Indexing Restricted Pages On

Re: [htdig] Indexing Restricted Pages

2000-12-20 Thread Dave Salisbury
Directory require valid-user order allow, deny deny from all allow from .your.domain.com /Directory or some such permutation. also add a "satisfy any" in the Directroy block. Thanks for the suggestion, Dave. If we do that, if I understand this correctly, it will