Re: [htdig] query parameters should be ignored by extension filter? - PATCH for 3.2.0b5

ces > Information Systems Services > University of Southampton > > - Original Message - > From: "Gilles Detillieux" <[EMAIL PROTECTED]> > To: "ht://Dig mailing list" <[EMAIL PROTECTED]> > Sent: Tuesday, March 30, 2004 7:20 PM > Subject:

Re: [htdig] query parameters should be ignored by extension filter? - PATCH for 3.2.0b5

x" <[EMAIL PROTECTED]> To: "ht://Dig mailing list" <[EMAIL PROTECTED]> Sent: Tuesday, March 30, 2004 7:20 PM Subject: Re: [htdig] query parameters should be ignored by extension filter? - PATCH for 3.2.0b5 > According to me: > > Last week, I wrote: > > &g

Re: Fwd: [htdig] query parameters should be ignored by extension filter? - PATCH for 3.1.6

Toby Thain wrote: Begin forwarded message: *From: *Gilles Detillieux <[EMAIL PROTECTED]> *Date: *31 March 2004 4:12:58 AM *To: [EMAIL PROTECTED] (Toby Thain) *Cc: [EMAIL PROTECTED] (David Adams), [EMAIL PROTECTED] (ht://Dig mailing list) *Subject: Re: [htdig]

Re: Fwd: [htdig] query parameters should be ignored by extension filter?

According to Toby Thain: > >> David Adams wrote: > >> > >>> Toby, > >>> > >>> Did you have a valid_extensions: statement originally? If you did, > >>> then > > it > >>> might be worthwhile trying without it, > >> > >> No, I had no valid_extensions originally. The query URLs were ignored > >> rega

Re: [htdig] query parameters should be ignored by extension filter? - PATCH for 3.2.0b5

According to me: > Last week, I wrote: > > According to David Adams: > > > I am also using ht://Dig version 3.1.6 and for me it IS indexing URLs like > > > > > > http://www.soton.ac.uk/~lopsoc/gallery.php?gallery=sorcerer1&photo=CNV00023.jpg > > > > > > even though I have .jpg in my bad_extension

Re: [htdig] query parameters should be ignored by extension filter? - PATCH for 3.1.6

Last week, I wrote: > According to David Adams: > > I am also using ht://Dig version 3.1.6 and for me it IS indexing URLs like > > > > http://www.soton.ac.uk/~lopsoc/gallery.php?gallery=sorcerer1&photo=CNV00023.jpg > > > > even though I have .jpg in my bad_extensions: list. > > Actually, I find

Re: Fwd: [htdig] query parameters should be ignored by extension filter?

ng Flash files? David Adams Corporate Information Services Information Systems Services University of Southampton - Original Message - From: "Toby Thain" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Saturday, March 27, 2004 8:22 AM Subject: Re: Fwd: [htdig] q

Re: Fwd: [htdig] query parameters should be ignored by extension filter?

From: "David Adams" <[EMAIL PROTECTED]> To: "Toby Thain" <[EMAIL PROTECTED]>, <[EMAIL PROTECTED]> Subject: Re: Fwd: [htdig] query parameters should be ignored by extension filter? Date: Fri, 26 Mar 2004 10:10:01 - - Original Message - Fro

Re: Fwd: [htdig] query parameters should be ignored by extension filter?

- Original Message - From: "Toby Thain" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, March 25, 2004 10:49 PM Subject: Re: Fwd: [htdig] query parameters should be ignored by extension filter? > David Adams wrote: > > > Toby, >

Re: Fwd: [htdig] query parameters should be ignored by extension filter?

a catch-all list as we are responsible for all site content. Toby - Original Message - From: "Toby Thain" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, March 25, 2004 12:49 AM Subject: Re: Fwd: [htdig] query parameters should be ignored by extension fi

Re: Fwd: [htdig] query parameters should be ignored by extension filter?

list of 108 bad extensions if anyone is interested, but I make no claims that it is anywhere near complete. - Original Message - From: "Toby Thain" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, March 25, 2004 12:49 AM Subject: Re: Fwd: [htdig] query p

Re: [htdig] query parameters should be ignored by extension filter?

oby Thain" <[EMAIL PROTECTED]> Sent: Wednesday, March 24, 2004 9:42 PM Subject: Re: [htdig] query parameters should be ignored by extension filter? > According to David Adams: > > I am also using ht://Dig version 3.1.6 and for me it IS indexing URLs like > > > > htt

Re: Fwd: [htdig] query parameters should be ignored by extension filter?

Toby Thain wrote: Begin forwarded message: *From: *"David Adams" <[EMAIL PROTECTED]> *Date: *24 March 2004 9:18:17 PM *To: *<[EMAIL PROTECTED]>, "Toby Thain" <[EMAIL PROTECTED]> *Subject: Re: [htdig] query parameters should be ignored b

Re: [htdig] query parameters should be ignored by extension filter?

According to David Adams: > I am also using ht://Dig version 3.1.6 and for me it IS indexing URLs like > > http://www.soton.ac.uk/~lopsoc/gallery.php?gallery=sorcerer1&photo=CNV00023.jpg > > even though I have .jpg in my bad_extensions: list. Actually, I find this surprising. Upon looking at th

Re: [htdig] query parameters should be ignored by extension filter?

University of Southampton - Original Message - From: "Toby Thain" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, March 24, 2004 9:58 AM Subject: [htdig] query parameters should be ignored by extension filter? > List, > > I noticed today t

[htdig] query parameters should be ignored by extension filter?

List, I noticed today that htdig is not indexing URLs like: /foo/page.php3?f=bar.jpg because it notices the URL ends with ".jpg". I am surprised that it's not smart enough to realise that the fetched object is actually a ".php3", and I definitely want that URL followed. Is this fixed in a rec

Re: [htdig] query string parameter delimiter

According to Craig Wallace: > 5.21 in the FAQ says both ; and & (though it doesn't say & which would > be prefereable) You can of course use & which should get translated to "&" by the web browser. No problems there. Even if for some reason it wasn't translated, and htsearch saw a raw "&" in the

[htdig] query string parameter delimiter

Hi, 5.21 in the FAQ says both ; and & (though it doesn't say & which would be prefereable) can be used as a variable delimiter inthe next and previous button links generated by htsearch, but where can this be configured? Thanks, Craig This document should only be read by those persons to whom i

Re: [htdig] query

On Saturday, November 9, 2002, at 12:07 AM, Prabhat Sharma wrote: When i search for something using the htsearch engine, it gives the ipaddress first and then the path of the file. i want to replace the ipaddress with the site name eg: abc.com. Have you looked at the search_rewrite_rules attrib

[htdig] query

Hi, When i search for something using the htsearch engine, it gives the ipaddress first and then the path of the file. i want to replace the ipaddress with the site name eg: abc.com. What can be done to replace the same 11/08/02, 4269 bytes regds, Prabhat

Re: [htdig] Query

Vipul Patel's bits of Tue, 7 May 2002 translated to: >Sir/Madam, > The document says that in DIGGING process it creates >a database, Which database is it ? Is it maintaing any >RDBMS or what ? ht://Dig uses Berkeley DB, which is not a RDBMS. Jim _

[htdig] Query

Sir/Madam, The document says that in DIGGING process it creates a database, Which database is it ? Is it maintaing any RDBMS or what ? Please reply me asap. thanks, Vipul For live cricket scores download Yahoo! Score Tr

Re: [htdig] query string weirdness

According to Brian White: > The "; instead of &' intrigued me so I went hunting on W3C to find > a definitive standard that spelt out the format of the query part > of a HTTP URI - and failed. > > I looked at the HTML 4.01 docs, and an RFC on URI's ( which said > that ';' was a reserved character

Re: [htdig] query strings that start with semicolon

On Mon, 5 Feb 2001, Richard Seymour wrote: > But the separator between the cgi program name and the query string > component should still be a "?" -- is that what you're saying? If so, > the software, I'm using is broken, which wouldn't surprise me. Correct. The separator between a URL and the

Re: [htdig] query strings that start with semicolon

Geoff Hutchison wrote: > > On Mon, 5 Feb 2001, Richard Seymour wrote: > > > Previous software I have used would create something like: > > > > http://www.foo.com/cgi-bin/htsearch?jsessionid=xYzXyzxYzXyzxYzXyz > > > > with a question mark instead of a semicolon. > > > > All the links with semicol

Re: [htdig] query strings that start with semicolon

On Mon, 5 Feb 2001, Richard Seymour wrote: > Previous software I have used would create something like: > > http://www.foo.com/cgi-bin/htsearch?jsessionid=xYzXyzxYzXyzxYzXyz > > with a question mark instead of a semicolon. > > All the links with semicolons in them work *except htdig*. You mean

[htdig] query strings that start with semicolon

When users of my site don't use cookies, my java servlet engine adds a session id to all links (including the one to /cgi-bin/htsearch), so they look like this: http://www.foo.com/cgi-bin/htsearch;jsessionid=xYzXyzxYzXyzxYzXyz Previous software I have used would create something like: http://ww

Re: [htdig] query string weirdness

as well as the document. Dave - Original Message - From: Brian White <[EMAIL PROTECTED]> To: Geoff Hutchison <[EMAIL PROTECTED]>; Dave Salisbury <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Tuesday, January 30, 2001 10:27 PM Subject: Re: [htdig] query stri

Re: [htdig] query string weirdness

The "; instead of &' intrigued me so I went hunting on W3C to find a definitive standard that spelt out the format of the query part of a HTTP URI - and failed. I looked at the HTML 4.01 docs, and an RFC on URI's ( which said that ';' was a reserved character in a "query" , but that was it ) An

Re: [htdig] query string weirdness

On Tue, 30 Jan 2001, Dave Salisbury wrote: > for some reason the %7C gets thrown in there too (???). The %7C is the proper URL-encoded form of the '|' character. > But the main problem is the ";" instead of "&" separator. > > There seems to be some url document encoding going on that > I would

[htdig] query string weirdness

running 3.1.5 on solaris I'm getting funny query strings in the search results: /Display.pl?Zoom=World_Oceania_AU&mode=I&lang=en&nav=1 interestingly they seem to work. but then down lower in the Pages: numbered images I get href="?restrict=lang%3Den;exclude=%7Cnav%3D0;config=htdig;method=and;