Re: [htdig] Wrappers and htdig 1.3.5

Subject: Re: [htdig] Wrappers and htdig 1.3.5
From: Brandon Bell (
Date: Sun Apr 23 2000 - 08:49:47 PDT

Thanks for the feedback Edmond.

I think the only solution is to hack the htdig code as you suggest below and
revert the separator back to the '&'.

If I use Version 2.64, which apparently does allow for the semicolon
separator, I still have the problem that when HTML forms are submitted the
ampersand is used, but when next/prev page clicks are done from the search
results page the semicolon is used. Because of this inconsistency, writing
any wrapper seems next to impossible to handle both cases at the same time.

----- Original Message -----
From: Edmond Abrahamian <>
To: Brandon Bell <>
Cc: <>
Sent: April 22, 2000 11:00 PM
Subject: Re: [htdig] Wrappers and htdig 1.3.5

> On Sat, 22 Apr 2000, Brandon Bell wrote:
> > * Made some attempts to get htsearch's output to be more HTML 4.0
> > compliant. It quotes all HTML tag parameters, and uses ";" instead of
> > as parameter separator in URLs for next pages. Reserved characters in
> > parameters are now encoded. Please note that this may break a variety of
> > CGI wrappers, for example, those written in PHP3.
> The quotes were not a problem for me, but the ';' was. In my case, Perl's
> module could not handle this separator. I looked at the latest
> version's documentation, and it did not seem to have an option to specify
> a different parameter separator than '&'. My only recourse was to change
> htsearch. This is really very easy. In, the (small) method
> Display::createURL needs to be changes to use '&' instead of ';'.
> > I'm using a PERL wrapper and GET for my form submission method so I can
> > analyze what people are searching for. My PERL wrapper handles the
> > search request just fine, but of course chokes big time when you try to
> > move to another page due to the change in the URL encoding there.
> Another way is to change, or even the wrapper if you are parsing
> the QUERY_STRING yourself. In my case, changing was the easiest
> (and laziest) thing to do...
> I think the correct way to do it (at least in my case, and IMHO) is to
> change the perl CGI module to be able to be told what the separator it
> should be looking for looks like.
> In any case, I believe you would still run into the same problem with
> as it wants to write out the query string in the same format, but the CGI
> program reads it in from stdin.
> edmond

To unsubscribe from the htdig mailing list, send a message to
You will receive a message to confirm this.

This archive was generated by hypermail 2b28 : Sun Apr 23 2000 - 06:40:25 PDT