[www-html] <none>

At 08:15 PM 12/23/98 , kgeorge@tcpsoft.com wrote:
>Greg Marr wrote:
>> There is no need to URL-encode the ampersand.  It needs to be protected from
>> the HTML parser, not the network layers.  URL encoding it will only help 
>if you
>> write your script to handle it, and isn't a general-purpose solution.  Using
>> &amp; instead of & will protect it from the HTML parser, which is all that is
>> necessary.
>
>The original poster wanted to include the ampersand as part of the value
>of a name=value pair.  Since the ampersand is the name=value pair
>seperator in html, it is necessary to url encode it if you want an
>ampersand as part of the value.
>
>If name: x and value: hello&goodbye the value must be encoded so the
>ampersand is not lost and goodbye is not treated as a new argument.  I
>believe this is what he was asking.  The only thing that &amp; is good
>for is for use in web pages.  It can not be used for encoding a url
>because a) it contains the ampersand itself and b) it is translated to a
>"&" before the form/url is queried.
>
>If you want to have name=value&thisvalue as a name value pair, the
>_only_ way to accomplish this is to say name=value%26thisvalue and then
>decode it in your cgi program.
>
>Kyle George
>kgeorge@tcpsoft.com
X-Sender: gregmm@pop.ma.ultranet.com
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 
Date: Mon, 28 Dec 1998 10:02:33 -0500
To: kgeorge@tcpsoft.com
From: Greg Marr <gregm@alum.wpi.edu>
Subject: Re: &-separator from a form
Cc: www-html@w3.org
In-Reply-To: <36819598.6C508021@tcpsoft.com>
References: <Pine.LNX.3.96.981222214956.17798K-100000@ch.twi.tudelft.nl>
 <4.1.19981223084336.00e22c70@pop.ma.ultranet.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"

At 08:15 PM 12/23/98 , kgeorge@tcpsoft.com wrote:
--
Greg Marr
gregm@alum.wpi.edu
"We thought you were dead." 
"I was, but I'm better now." - Sheridan, "The Summoning"

Received on Monday, 28 December 1998 10:07:06 UTC