Phil Endecott wrote:
There is not much to go on in terms of specifications. The closest is
RFC1738, which includes BNF for a file: URI. However it is ten years
old, so whether it reflects current practice I do not know. But it does
not allow ; in file: URIs.
I conclude from this that
Dear All,
There are now two threads here so I'm splitting it into two messages.
Phil I conclude from this that wget should be replacing ; with
Phil its %3b escape sequence.
Tony I think you're confusing what wget is required to do with
Tony URLs entered on the command line and what it chooses
(2) There are now two threads going on here so I'm splitting it into two messages.
Phil Tony, are you suggesting that this is legal HTML?
Phil a href=http://foo.foo/foo.cgi?p1=v1p2=v2;Foo/a
Phil I'm fairly confident that you need to escape the to make it
Phil valid, i.e.
Phil a
i originally sent the following email with patch 1.5 weeks ago to
[EMAIL PROTECTED], but as i haven't received a reply nor has cvs
been updated since that time (Hrvoje Niksic may be on vacation or busy),
i'm sending this to the users' list as someone might be interested in it
(as i'm sure i'm not
