Evert Rol wrote:
> I was afraid so. I guess somewhere along the line, things have to be
> decoded anyway.
> I have little say over the ID, so I cannot really prevent a slash or %
> 2f occurring (or simply tell how many there'll be).
> For the moment, I took Ron's idea and use map.connect
> (':controller/:action/*id'), but I guess that may prevent some Routes
> functionality (eg like an automatic 404).
> Funny thing is, with this solution, when I actually use encoded
> slashes for such a URL, as the example above, I get a 404. When I use
> a proper forward slash (/finder/select/R/2007/23), I get the correct
> response. Rather unexpected; I guess I'll have to dig more into what
> happens along the way.
>
If you have possibly encoded arguments like this, your best bet is to
have them as query arguments as the query string will be handled as
you'd expect with forward slashes.
HTH,
Ben
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"pylons-discuss" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/pylons-discuss?hl=en
-~----------~----~----~----~------~----~------~--~---
