" If i remember correctly, that code was here as PATTERN was always ending with an additional /. I have to suppose that this is not (or never was) a rule. Maybe the best choice would be adding a condition. "
Are you suggesting an if that checks whether or not the last character of PATTERN is a '/' ? This seems reasonable to me. Looking at the example mongrel2 config (http://mongrel2.org/static/book-finalch4.html#x6-210003 -- Source 10), some of the handlers do not have an ending slash. Specifically, the rule for the handler demo uses '/handlertest' as the pattern. I could put a '/' on the end of my route prefix for my handler. The convention for some tools is a trailing '/' indicates serving up a directory, and no trailing '/' indicates a file or app. However, it appears that the routing method used by mongrel2 does not have explicit requirements for the route prefix used by handlers. In other words, I can try it with the trailing '/' for my handler route, and if that works, just document it somewhere that uwsgi requires a trailing slash for the route prefix or should the if statement be put in that checks whether or not a route prefix has a trailing '/'? Regards, Jeff Van Voorst _______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
