From: Ted Stresen-R. <bow...@ho...> - 2002-04-23 00:02:20
|
1) You can set the argument separator for php in the php.ini file as in the following: arg_separator.output = ";" arg_separator.input = ";" (be sure to use the quotes as the semi-colon is seen as an "end of line" marker in the php.ini file) 2) Depending on your configuration, you may be able to do (1) on a directory-by-directory basis using the .htaccess file (php.net has more info on how to do this, http://www.modwest.com/help/kb.phtml?cat=1&qid=44 but this article may be more helpful). 3) You can also uses ini_set(arg_separator.input) = ";" (and ini_get()) to set the argument separator right in a php page, but note that if you are trying to set these values after a page has been returned to the browser from htsearch, you may be too late as the page has already been parsed by both htsearch and the web server (and PHP). http://www.modwest.com/help/kb.phtml?cat=5&qid=98 For susansexton.com, we just went ahead and changed it in the php.ini file so that we would be compliant and not worry about it anymore... For details on how we set up PHP to work with htdig, check out http://dev.susansexton.com/htdig/ Ted Stresen-Reuter (trying really hard to provide quality feedback ;-) On 4/22/02 3:05 PM, "Christopher Murtagh" <chr...@mc...> wrote: > On Fri, 15 Mar 2002, Gilles Detillieux wrote: >> According to Christopher Murtagh: >>> So, what I did instead was modify the Display.cc file in htsearch so that >>> it generated properly formatted query strings. All this meant was changing >>> ';' for '&' in the Display::createURL method (16 of them to change). >> ... >>> Maybe it would be nice to have a config option in 3.2 where it could >>> compile a php friendly version? Just a thought. >> >> Are you using the latest version of PHP? I thought I had read previously >> on this list that it now can parse CGI parameters separated by semicolons. >> Maybe I'm remembering wrong? I know the latest CGI.pm for Perl does. >> HTML 4.0 is hardly a new standard, and we've actually been slow to bring >> ht://Dig into compliance with it, so I don't know why other web application >> developers are so slow to get with the program. See FAQ 5.21 if you >> haven't already. > > > Hi Gilles, > > Thanks for the note... sorry it took so long for me to reply. Your reply > got filtered badly and I just saw it today! > > Sorry I didn't see the FAQ, I didn't realize that this was a PHP problem > not being compliant. FWIW, I tried the following with PHP version 4.1.2 > (the lastest): > > <HTML> > <? > print"foo: $foo<BR>"; > print"foobar: $foobar<BR>"; > ?> > </HTML> > > with this URL: > > http://server/file.php?foo=hey&foobar=there > > Output is as expected: > > foo: hey > foobar: there > > However, this URL: > > http://server/file.php?foo=hey;foobar=there > > produces: > > foo: hey;foobar=there > foobar: > > Perhaps there is a compile option in PHP? Anyone else solve this issue? A > compile time option with PHP maybe? > > 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 <htd...@li...> > To unsubscribe, send a message to > <htd...@li...> with a subject of unsubscribe > FAQ: http://htdig.sourceforge.net/FAQ.html > |