I have a "special" situation in an application that allows "/" characters in
usernames. If I define a URI that include a username as a path element, the
Router gets confused when presented with a URI with an encoded "/" (%2f);
something like http://localhost:8182/users/foo%2fbar/orders. Changing it to
http://localhost:8182/users/foo%2Fbar/orders works, however.
Is there a reason for the case sensitivity? RFC 1738 suggests that lowercase
hexadecimal be accepted also.
I happened on this behavior when typing URIs into a browser. I'm going to look
at a possible work-around if I need it; probably a custom filter placed ahead
of the router. If there is a better approach, please let me know.
Thanks,
Paul
____________________________________________________________________________________
Boardwalk for $500? In 2007? Ha! Play Monopoly Here and Now (it's updated for
today's economy) at Yahoo! Games.
http://get.games.yahoo.com/proddesc?gamekey=monopolyherenow
