| Subject: | Small diff to document the fact that arguments aren't uri-unescaped |
Here's a little documentation patch to keep people, who aren't sure
if arguments are uri-unescaped automatically, from searching if they would
introduce double-unescaping by unescaping explicitely.
Would have saved me a few head scratches :-)
Regards,
Simon
| Subject: | lib_Catalyst_Request_pm.diff |
Index: lib/Catalyst/Request.pm
===================================================================
--- lib/Catalyst/Request.pm (revision 8631)
+++ lib/Catalyst/Request.pm (working copy)
@@ -111,6 +111,9 @@ For example, if your action was
and the URI for the request was C<http://.../foo/moose/bah>, the string C<bah>
would be the first and only argument.
+Arguments just get passed through and B<don't> get unescaped automatically, so
+you should do that explicitely.
+
=head2 $req->args
Shortcut for arguments.