-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Lucas,
To use + as a space is correct within the query, but is correct
within the path.
Huh?
- -chris
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.7 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
From: Christopher Schultz [mailto:[EMAIL PROTECTED]
Subject: Re: Encoding issue: + versus %20
To use + as a space is correct within the query, but is correct
within the path.
Huh?
I think a rather critical not was left out of the second part of the
sentence.
- Chuck
Mmmm..
It should read:
To use + as a space is correct within the query, but is not correct
within the path.
- LG
On 6/7/07, Christopher Schultz [EMAIL PROTECTED] wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Lucas,
To use + as a space is correct within the query, but is correct
Short answer:
An URL has many part, one part that is called path (in this case
upload/a b.jpg) and another part is called query (that is usually
what is after the ? in a URL) These two parts use slightly different
reserved characters that may, should, or must be escaped under
different rules. To
Does that mean there's no way to load images with file names that contains
spaces then? I'm not understanding something here. Because if i include a
link to a graphic image whose filename contains spaces, it uses +, and
tomcat refuses to the load image; however if I replace it with %20, then it
hstang [EMAIL PROTECTED] wrote in message
news:[EMAIL PROTECTED]
Does that mean there's no way to load images with file names that contains
spaces then? I'm not understanding something here. Because if i include
a
link to a graphic image whose filename contains spaces, it uses +, and
