I finally had some time to sit down and do some ht://Dig work. I've been
swamped with getting our server back to speed after several accounts were
compromised. :-( It turns out someone managed to slip a packet sniffer onto
our network. <ugh>
Anyway, I cleaned out the incoming folder of the bug system. This was one
of the messages posted.
Is this correct? If so, what should we do about it? We can't use | because
that already has a meaning for ht://Dig. Furthermore, we'll still have to
parse & separators because many browsers (and a *lot* of URLs) still use it.
Anyone have a good suggestion for a separator? I'd go for * offhand, but I
might be missing some horrible consequence (I was going to suggest # first
and realized the error of my ways).
-Geoff
Date: Sat, 3 Apr 1999 20:15:05 -0800
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: PRIVATE: Use of & as CGI variable separator vs. HTML 4.0
Full_Name: Fred Condo
Version: 3.1.1
OS: FreeBSD 2.2.8
Submission from: pm3dyn102.dip.csuchico.edu (132.241.249.102)
HTML 4.0 strict does not permit the & character in the URLs generated as CGI
variable separators for the page list. This is because the & introduces a
general entity.
W3C recommend rewriting the code to use a different separator, such as | or ;
that does not have special meaning in HTML.
Until this is done, ht://dig cannot emit valid HTML 4.0 (strict).
------------------------------------
To unsubscribe from the htdig3-dev mailing list, send a message to
[EMAIL PROTECTED] containing the single word "unsubscribe" in
the SUBJECT of the message.
