--nextPart1805012.Nm3FZB8HC5
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

On Wednesday 15 September 2004 1:14 am, Robert Clark wrote:
> On Tue, 2004-09-14 at 19:09, Christian Parpart wrote:
> > well, this is a rather odd problem I actually have.
> > So, I must be able to get arguments containing a # as argument value,
> > e.g.
>
> [ snip ]
>
> > So, finally I got it by URL encoding the '#' into a "%23", but my
> > question now is, WHAT chars "are declared to be invalid" in URL
> > arguments, and though, "has to be" encoded in the well known way?
>
> RFC 1738 defines how URLs are to be encoded. It has the following
> paragraphs:
[snip]

Well, that's what I obviousely had to read.

Thanks alot ;)
Christian Parpart.

=2D-=20
 01:42:46 up 21 days, 13:22,  3 users,  load average: 0.10, 0.25, 0.27

--nextPart1805012.Nm3FZB8HC5
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)

iD8DBQBBR4ItPpa2GmDVhK0RAvicAJ9CULztb2s3LRWPs7p7759jckZ/iACeP38P
LGayLjV2ByaaaaiO4R6D9To=
=ph2S
-----END PGP SIGNATURE-----

--nextPart1805012.Nm3FZB8HC5--