Tony Lewis [EMAIL PROTECTED] writes:
Phil Endecott wrote:
Tony The stuff between the quotes following HREF is not HTML; it
Tony is a URL. Hence, it must follow URL rules not HTML rules.
No, it's both a URL and HTML. It must follow both rules.
Please see the page that I cited in my
-Original Message-
From: Phil Endecott [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 30, 2004 9:06 AM
To: [EMAIL PROTECTED]
Subject: Re: Escaping semicolons
[SNIP]
This makes me wonder how Internet Explorer copes. I don't have a
Windows machine here, so I wonder if someone
Phil This makes me wonder how Internet Explorer copes.
Dave IE 6 opens the other file. Mozilla 1.7 says the file cannot be found.
Thanks Dave! I have submitted a Mozilla bug report:
http://bugzilla.mozilla.org/show_bug.cgi?id=249239
I'll let you know if they think it's a wget bug.
--Phil.
[mailto:[EMAIL PROTECTED]
Sent: Monday, June 28, 2004 10:17 PM
To: Phil Endecott; [EMAIL PROTECTED]
Subject: Re: Escaping semicolons (actually Ampersands)
Phil Endecott wrote:
Tony The stuff between the quotes following HREF is not HTML; it is a
Tony URL. Hence, it must follow URL rules
Tony The stuff between the quotes following HREF is not HTML; it
Tony is a URL. Hence, it must follow URL rules not HTML rules.
No, it's both a URL and HTML. It must follow both rules.
Please see the page that I cited in my previous message:
Phil Endecott wrote:
Tony The stuff between the quotes following HREF is not HTML; it
Tony is a URL. Hence, it must follow URL rules not HTML rules.
No, it's both a URL and HTML. It must follow both rules.
Please see the page that I cited in my previous message:
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
Dear wgetters,
A few days ago I asked about whether wget should escape semicolons in filenames that
it downloads. I didn't get many replies, so I have done some research and have
concluded that it probably should be escaping them.
There is not much to go on in terms of specifications. The
Dear Wget experts,
I am using wget to build a downloadable zip file for offline viewing of a
CGI-intensive web site that I am building.
Essentially it works, but I am encountering difficulties with semicolons. I use
semicolons in CGI URIs to separate parameters. (Ampersand is more often used
-Original Message-
From: Phil Endecott [mailto:[EMAIL PROTECTED]
Sent: Thursday, June 24, 2004 11:05 AM
To: [EMAIL PROTECTED]
Subject: Escaping semicolons
[SNIP]
First question: is ; an acceptable character in Windows
filenames? ( I don't have a Windows machine to try
Phil Endecott wrote:
I am using wget to build a downloadable zip file for offline viewing of
a CGI-intensive web site that I am building.
Essentially it works, but I am encountering difficulties with semicolons.
I use semicolons in CGI URIs to separate parameters. (Ampersand is more
often
13 matches
Mail list logo
