I have a string I want to use as one argument to a controller. It's user-sourced and occasionally has slashes in.<br><br>I use this as <br><br> $c->uri_for('/controller/action', 'string/with/slashes');<br>
<br>(done in TT, as it happens, but the results are the same)<br><br><br>I'd like that argument to be the first argument of my controller. uri_for doesn't encode the slashed string, so that gives me /controller/action/string/with/slashes, and misses my one-argument action.<br>
<br>If I URI-encode it, things work better in the Catalyst webserver, <app>_<a href="http://server.pl">server.pl</a><br><br>$c->uri_for('/controller/action', 'string%2Fwith%2Fslashes');<br><br>The url is then /controller/action/string%2Fwith%2Fslashes and the action is found; Catalyst even decodes it, and we're laughing.<br>
<br>However, this leads to weird things happening. If you run under lighttpd/fastcgi, it thoughtfully decodes the slashes for you, which brings us back to the first case: it misses my 1-argument controller and gets me a 404. Catalyst reports:<br>
<br>[debug] "GET" request for "content/series/David%20Audley%20/%20Jack%20Butler:%20Chronological%20Order" from "xx.xx.xx.xx"<br>[debug] Path is "/"<br>[debug] Arguments are "content/series/David Audley / Jack Butler: Chronological Order"<br>
<br>Now, one answer to this is to encode slashes in such strings as non-uri-encoding. Another is to have special-case actions that can have slashed arguments in them. A third would be to change lighttpd's behaviour - there's a bug open for exactly that but no activity on it; also, I suspect other webservers behave similarly...<br>
<br><br>Has anyone come up against this before? Any tips?<br><br>Cheers,<br>-- <br>Ian.<br>