[hunchentoot-devel] Probably a bug in url-encode/url-decode

[Jordan Powell]

Try Javascript escape/unescape. There's still an issue with + but that's 
the only one.

I tend to just use a regex replace in the Javascript to replace + with 
some uncommon string before sending it to the server and then doing the 
reverse replacement when I get the string back. For all other symbols I 
tried, escape/unescape matched url-encode/url-decode.

Jordan

On 03/19/2010 08:36 AM, Andrey Moskvitin wrote:
> > No, it just depends on which RFC you follow that describes URL
> > escaping.
>
> Which? In JavaScript used encodeURI for URL and encodeURIComponent
> for single components. hunchentoot:url-decode does not match any
> of these functions. Browser does not replace # \+ to "%2B" in header
> when sending request to the server. A substitute # \ + at # \ Space,
> as does hunchentoot:url-decode, need for forms, but not for the url.
>
> I have wrong understanding?
>
> Andrey
>
>
> _______________________________________________
> tbnl-devel site list
> tbnl-devel at common-lisp.net
> http://common-lisp.net/mailman/listinfo/tbnl-devel

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.common-lisp.net/pipermail/tbnl-devel/attachments/20100319/49d1ce56/attachment.html>