My apologies if this has been sent twice.  Near as I can tell, the first 
time I accidentally mailed it direct to Giles and not to the entire list as 
I intended.

At 04:40 PM 6/18/01 -0500, you wrote:
>According to Jerry Asher:
> > What standard suggests that URL variables should be separated with 
> anything
> > other than an ampersand?
>
>http://www.w3.org/TR/REC-html40/appendix/notes.html#h-B.2.2
>
> > May I ask why htsearch is using semicolons to separate the config, page,
> > and words url variables?
>
>http://www.htdig.org/FAQ.html#q5.21
>
> > Is there anyway to make yet another config option to htsearch to specify
> > the url variable separator used in making the next page links?
>
>There's always a way if you're willing to code it yourself.  It is open
>source after all.  None of the developers see this as a problem that's
>worth spending a lot of their time on, as the workarounds are available,
>easy, and better than backing out the changes to htsearch to make it go
>back to the old, non-standard approach.

Thank you.  Interesting. I found the entry in the FAQ that points to the 
HTML 4 spec which sure enough "suggests" that webservers support semicolons 
and that applications use semicolons and not ampersands.

I certainly don't want to get into an argument, but it appears from RFC 
1866 section 8.1.2 that the ampersands are the standard and that semicolons 
are a nonstandard "encouragement" and this is backed up by the example POST 
submission shown in 8.2.4 (http://www.ics.uci.edu/pub/ietf/html/rfc1866.txt)

So I would still think that using ampersands is the standard, but since I 
am probably wrong, can you tell me why you believe that using ampersands is 
in fact non-standard and that semicolons are the standard (and as a founder 
of the opennsd webserver project, I would like to be able to convince my 
fellow opennsd developers that we should be supporting semicolons and 
deprecating ampersands/)

Since you note that it is open source, is it reasonable for me to think 
that if I submit a good quality patch that supports ampersands as well as 
semicolons, it will be applied to the source?

Thank you,

Jerry Asher

=====================================================
Jerry Asher                       [EMAIL PROTECTED]
1678 Shattuck Avenue Suite 161    Tel: (510) 549-2980
Berkeley, CA 94709                Fax: (877) 311-8688


_______________________________________________
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

Reply via email to