On Tue, 23 Apr 2002, Gilles Detillieux wrote: >OK, so arg_separator.input works as a multiple-choice thingy, where any >one single character in the list works as separator (but & works whether >in the list or not). What do multiple characters in >arg_separator.output mean, though?
Good question, I'm not sure how to test this. I tried changing it to a bunch of different options, but I'm not sure where PHP would actually *use* arg_separator.output. If you make a FORM with the GET method, it is the browser that generates the query string (mozilla and every browser I know of uses '&'). >How do you test how arg_separator.output works? Dunno. >If I can get to the bottom of what the ideal settings for these are, I'd >like to add a note about this to FAQ 5.21. I would say that for the most part, the arg_separator.input should be ";&". >> So, now my search engine can fetch restrict values from Postgres that is >> aware of multiple sites that span across different servers, and I've >> hacked htsearch so that it doesn't put the restrict in the page URL >> (because it is generated by PHP/Postgres). I then simply have this code: > >Interesting. Normally, htsearch puts in the page URL any parameter that >it received as a CGI or URL parameter initially, so it doesn't propagate >parameters that aren't previously passed to it, but it doesn't allow for >the case where you'd want to pass it a parameter but not have it passed >back. I don't know if this would be a commonly needed feature - I don't >recall any earlier requests for it, or complaints about having to hack >it out of the code. I don't know how different my site is from anyone else's. I did have to pass an additional parameter as well. The allow_in_form config was really handy there, and I was just glad that the code was clean enough to be able to go and make the changes without any problems. :-) >In 3.1.6, you can turn off the content-type header that htsearch outputs. >See http://www.htdig.org/attrs.html#search_results_contenttype Very cool. Thanks! BTW, to see how we are using ht:/dig with Postgres and PHP, check out this URL: http://www.mcgill.ca/music-departments/jazz/ and perform a search on 'student' at the bottom of the page. The result page is color-coded for the site you came from, the title of the search site and search section comes from Postgres as well, and the restrict value will be (in this case) www.mcgill.ca/music-departments/. If you refine the search to the entire faculty, it will include a number of www.mcgill.ca/music-foo type dirs, but could also include www.music.mcgill.ca/foo. ht://Dig rocks. Thanks for all the work. Cheers, Chris -- Christopher Murtagh Webmaster / Sysadmin Web Communications Group McGill University Montreal, Quebec Canada Tel.: (514) 398-3122 Fax: (514) 398-2017 _______________________________________________ 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
