Hi, ~flow wrote: > 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. If you want performance you probably want mod_wsgi :) I haven't discovered something with a similar good performance so far.
> 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. If the rule is defined with a trailing slash the rule matcher will only allow one trailing slash. Remove the trailing slash and it eats everything. This is a side-effect of the strict trailing slash processing and is here to stay. I don't think multiple trailing slashes are useful at all so I don't want to make the parser any more complex just for that edge case. > 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. WSGI provides the path info as unescaped value so there is no way to find out if the value was escaped or not. If this is here to stay I don't know, there are intentions to change it on the web sig. > i had a look into the source but i'm not sure where to fix this---any > pointers what to look for? I don't think that's a bug and I don't feel like I want to have a "fix" for that in Werkzeug. The routing system is already more complex than it has to be. Besides, I think web servers are free to normalize multiple slashes into one. > cheers & ~flow Regards, Armin --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
