[Seaside] is there url encoding in Seaside or Squeak?
boris at deepcovelabs.com
Wed Oct 3 14:57:46 UTC 2007
Really? I use existing encoding to pass URLs to Flash components via vars and never noticed needing to change encoding to include underscore and period chars as it worked just fine so far.
(Sent from a BlackBerry)
----- Original Message -----
From: seaside-bounces at lists.squeakfoundation.org <seaside-bounces at lists.squeakfoundation.org>
To: Seaside - general discussion <seaside at lists.squeakfoundation.org>
Sent: Wed Oct 03 04:50:34 2007
Subject: Re: [Seaside] is there url encoding in Seaside or Squeak?
On Oct 3, 2007, at 12:30 PM, Stuart Herring wrote:
> On 9/30/07, Merik Voswinkel <merik at mac.com> wrote:
>> My mistake because I was looking for something to encode the whole
>> url, not one character.
>> After two hours I have found what I was looking for: String>>>
>> encodeForHTTP encodes the whole string:
>> xmlUrl := xmlUrl encodeForHTTP.
>> But it does not encode all (just like Seaside), it does not encode
>> the '_' and the '.' as you can see from this result:
>> So I will rewrite it to encode those characters as well, like the
>> tool at http://www.dommermuth-1.com/protosite/experiments/encode/
>> index.html .
>> This tool is written in Flash and does encode the '_' and '.' also.
>> I need the conversion Flash uses because it is for passing url's with
>> FlashVars to Flash.
>> The question that remains is why some characters are not encoded and
>> others are.
> Why would you encode '_' or '.'? They have no special meaning in a
> URL or in HTTP and they both fall within the 7 bit ASCII character set
> as standard printable characters.
> Encoding them would produce a needlessly long URL and waste CPU cycles
> at both ends.
It is what FlashVars demand (I think it is typical of Adobe Flash, i
vastly prefer Open Source Flash)
>> From the RFC you quoted above:
> Thus, only alphanumerics, the special characters "$-_.+!*'(),", and
> reserved characters used for their reserved purposes may be used
> unencoded within a URL.
> '_' and '.' are explicitly mentioned as not needing to be encoded
It still must be done, i tested it. Flashvars is not documented so
this is how you must find out.
I have it running and implemented a special encodeForHTTPandFlashVars
>> From your examples it's apparent that you don't want _every_
> encoded as you're not expecting the standard alpha-numeric characters
> to be encoded, so why underscore and full-stop?
Again, it must be so as the tests prove.
Seaside mailing list
Seaside at lists.squeakfoundation.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the seaside