Just found out that this is probably rather a mod_jk/tomcat issue.
Just for the archive:
I had to change +ForwardURICompat to +ForwardURICompatUnparsed in my
mod_jk apache settings (debian and gentoo use the first one as
default). Afterwards mod_jk will forward uris to tomcat fully encoded
and restlet will match uris just as expected.
On 8/10/07, Stefan Podkowinski <[EMAIL PROTECTED]> wrote:
> Hello
>
> Can someone give me some clues what I might be doing wrong or
> missunderstanding with this little problem?
>
> I've created a mapping for my restlet as follows:
>
> /browse/{year}/{city}/{street}
>
> now when I request the url everything works fine as long as I use
> plain ascii characters in the url, e.g.
> /browse/2007/london/victoriast
>
> Perfect so far. However, when I use non-ascii characters, the uri will
> not match. E.g.:
> /browse/2007/d%FCsseldorf/k%F6
>
> Why is this the case?
>
> I've debugged Template.java and the following regex pattern is being used:
> /browse/((?:[a-zA-Z0-9\-\.\_\~\!\$\&\'\(\)\*\+\,\;\=\:[EMAIL
> PROTECTED]|(?:\%[0-9ABCDEF][0-9ABCDEF]))+)/((?:[a-zA-Z0-9\-\.\_\~\!\$\&\'\(\)\*\+\,\;\=\:[EMAIL
>
> PROTECTED]|(?:\%[0-9ABCDEF][0-9ABCDEF]))+)/((?:[a-zA-Z0-9\-\.\_\~\!\$\&\'\(\)\*\+\,\;\=\:[EMAIL
> PROTECTED]|(?:\%[0-9ABCDEF][0-9ABCDEF]))+)
>
> Any ideas?
>
> Stefan
>
