Comment 2 for bug 797419

I can confirm the reported failure depends on the particular version of routes.
The error does not occur when using routes 1.12

It seems there is a bug in routes 1.10 which causes an invalid regexp to be generated when format extensions are used in the mapper.connect call.

I am currently evaluating the best course of action:
1) put routes 1.12 as a requirement
2) Fix code in a way that the API works with routes 1.10 as well
3) provide a patch for routes 1.10