There is no difference.  Anything prefixed by a "%" is to be interpreted as
a prefix to a hex representation of an ascii character.  So, %20 would be a
space.  Spaces also have the inherent shortcut of "+".  So, either one is
correct and either one will work.

Regards,

Howie Hamlin
--
inFusion Project Manager; On-Line Data Solutions, Inc. (631)737-4668
www.CoolFusion.com
============================================================
Please vote for iMS in the Most Innovative category here:
*** http://www.sys-con.com/ColdFusion/readerschoice2000/ ***
============================================================
Check out inFusion Mail Server - the world's most configurable email server

----- Original Message -----
From: PC <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, August 04, 2000 12:42 PM
Subject: OT: Confusion about URL/FORM encoding ... "+" vs "%20"


> I am trying to resolve some confusion I have about encoding spaces in
> URLs --
>
> Can somebody shed light on the difference between
>
> %20
>
>
> and
>
> +
>
> If one uses a search FORM it appears that the browser translates to "+"
any
> spaces from a text control ... but if one constructs a url with a variable
> such as ...index.cfm?desc=#description#    the spaces in #description# are
> translated into %20's...
>
> If I am constructing a URL programatically to speak to a cgi -- should I
> encode with +'s or %20's ?
>
> TIA!!
>
> --------------------------------------------------------------------------
----
> Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/
> To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_talk or
send a message to [EMAIL PROTECTED] with 'unsubscribe' in
the body.

------------------------------------------------------------------------------
Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/
To Unsubscribe visit 
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_talk or send a 
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.

Reply via email to