<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<title></title>
</head>
<body text="#000000" bgcolor="#ffffff">
Try Javascript escape/unescape. There's still an issue with + but
that's the only one.<br>
<br>
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. <br>
<br>
Jordan<br>
<br>
On 03/19/2010 08:36 AM, Andrey Moskvitin wrote:
<blockquote
cite="mid:e0c33b911003190136h33cf73c4s7934705d4c6c8f59@mail.gmail.com"
type="cite">
<div>> No, it just depends on which RFC you follow that
describes URL</div>
<div>> escaping. </div>
<div><br>
</div>
<div>
<div>Which? In JavaScript used encodeURI for URL and
encodeURIComponent</div>
<div>for single components. hunchentoot:url-decode does not match any</div>
<div>of these functions. Browser does not replace # \+ to "%2B" in
header</div>
<div>when sending request to the server. A substitute # \ + at # \
Space, </div>
<div>as does hunchentoot:url-decode, need for forms, but not for the
url.</div>
<div><br>
</div>
<div>I have wrong understanding?</div>
<div><br>
</div>
<div>Andrey</div>
</div>
<div><br>
</div>
<pre wrap="">
<fieldset class="mimeAttachmentHeader"></fieldset>
_______________________________________________
tbnl-devel site list
<a class="moz-txt-link-abbreviated" href="mailto:tbnl-devel@common-lisp.net">tbnl-devel@common-lisp.net</a>
<a class="moz-txt-link-freetext" href="http://common-lisp.net/mailman/listinfo/tbnl-devel">http://common-lisp.net/mailman/listinfo/tbnl-devel</a></pre>
</blockquote>
<br>
</body>
</html>