21 Jul
2010
21 Jul
'10
3:46 p.m.
[...] Drakma doesn't provide a URL-ENCODE function [...] And after thinking about it, turns out it _does_, just doesn't expose it. The thinking is, I presume, that all URL-encoded data should pass
On 21 July 2010 13:28, Herbert Snorrason <methanal@gmail.com> wrote: through another interface that handles the cleaning? In any case, the attached patch updates url-encode to RFC3986 (or at least only passes that standard's "unreserved characters" through) and exposes it. With greetings, Herbert Snorrason