Hello fellow Schemers!
I may misunderstand things here, but isn't URL:ENCODE-STRING meant to
propertly encode characters that are special to urls? Examples would be
=, & and ; (which should all be encoded). However,
> (url:encode-string "a=b&b=c;c=d")
just echoes that string literally ("a=b&b=
> From:
> Date: Wed, 02 May 2012 13:21:32 +0200
>
> Hello fellow Schemers!
>
> I may misunderstand things here, but isn't URL:ENCODE-STRING meant to
> properly encode characters that are special to urls?
It was meant to "encode query string", not "encode arbitrary text"?
> [...] I'm trying to
Date: Wed, 02 May 2012 13:21:32 +0200
From:
I may misunderstand things here, but isn't URL:ENCODE-STRING meant to
propertly encode characters that are special to urls? Examples would be
=, & and ; (which should all be encoded). However,
> (url:encode-string "a=b&b=c;c=d")
You're confused because URL:ENCODE-STRING has nothing to do with "url
encoding", which the encoding used for
application/x-www-form-urlencoded (and which itself has nothing to do
with URIs).
As the code comment says, this is just a backwards compatibility
procedure for something that existed in th
On Wed, 2 May 2012 22:44:44 -0700, Chris Hanson wrote:
> You're confused because URL:ENCODE-STRING has nothing to do with "url
> encoding", which the encoding used for
> application/x-www-form-urlencoded (and which itself has nothing to do
> with URIs).
>
> As the code comment says, this is just
Actually the correct fix is
(let ((input (open-input-octets octets start end)))
which I've committed to HEAD.
On Thu, May 3, 2012 at 1:53 AM, wrote:
> On Wed, 2 May 2012 22:44:44 -0700, Chris Hanson wrote:
>> You're confused because URL:ENCODE-STRING has nothing to do with "url
>> encoding"
