> Hmmm, normally web servers would normalise the SCRIPT_NAME/PATH_INFO > What hosting solution are you using?
my hosting solution is called wsgiref, and its there to stay... unless i discover a similar thing that performs better. maybe with an nginx in front. no apache, no mod_xy. ok, i can do slash removal by myself before routing gets to see the url. but that doesn't change my point that the behavior of werkzeug routing is surprising in this respect. you see, the docs don't mention multiple slashes, they just state that slashes may be part of a <path:xxx> component. also of interest is that percent-escaping trailing slashes doesn't help, either. to my understanding, percent- escaping should cause a character to loose its meta-meaning---so you can have e.g. `#`es and `?`s in your url. it's unintuitive that this should work for anything *but* trailing slashes. i had a look into the source but i'm not sure where to fix this---any pointers what to look for? cheers & ~flow --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pocoo-libs" 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/pocoo-libs?hl=en -~----------~----~----~----~------~----~------~--~---
