IIRC, uWSGI strips off the matching part of the URI before handing off to the application.
On 29/03/2011, at 1:28 AM, Stefan de Konink <[email protected]> wrote: > Hi there, > > > I was doing webpy development with uwsgi. (Yes I know: don't do that ;) > > Now i'm using: > > default: uwgsi (that sounds simple right?) > > My trivial script: > > import web > > urls = ( > '/(.*)', 'hello' > ) > app = web.application(urls, globals()) > web.config.debug = True > > class hello: > def GET(self, name): > if not name: > name = 'World' > return 'Hello, ' + name + '!' > application = app.wsgifunc() > > > And it is all nicely started. > [pid: 1085|app: 0|req: 3/3] 83.80.160.11 () {54 vars in 1091 bytes} [Mon Mar > 28 16:09:36 2011] GET / => generated 9 bytes in 2 msecs (HTTP/1.1 404) 1 > headers in 51 bytes (0 async switches on async core 0) > > Still I get 404 messages. Odd isn't it? > > > Now with a bit of creativity I ended up with removing the '/' before the (.*) > and suddenly everything worked. > > Can someone elaborate on this any further? This is plainly bizarre. > > > Stefan > _______________________________________________ > Cherokee mailing list > [email protected] > http://lists.octality.com/listinfo/cherokee _______________________________________________ Cherokee mailing list [email protected] http://lists.octality.com/listinfo/cherokee
