1 Sep
2004
1 Sep
'04
7:48 p.m.
On 2004-09-01 20:50:24, Edi Weitz wrote:
Yes, that's how the browser sends the field's name. When accepting POST or GET parameters the values are URL-decoded (see request.lisp and the function FORM-URL-ENCODED-LIST-TO-ALIST in util.lisp), the names aren't. Do you think it would make sense to decode the names as well? It'd be a trivial code change but I'm not sure about the implications. What do the RFCs say? Are there any restrictions on the names of the parameters?
Haven't read the RFC, but cgi.rb (CGI library of Ruby) decodes names and values.
key, value = pairs.split('=',2).collect{|v| CGI::unescape(v) }
CGI.pm (CGI library of Perl), too.
$param = unescape($param); $value = unescape($value);
Regards, Stefan