The wsgi middleware is really not the web2py way of doing this. It is a compatibility mode of allowing third party middleware of interoperating with web2py. It has only been tested in simple cases. It was recently rewritten (untested) nobody uses it, and I am considering dropping the feature.
Please tell us more what kind of interception you want to do. In my view some can be done at the web server level, some at the routes.py level and some at the response._caller level. On Monday, 5 August 2013 21:44:15 UTC-5, Marcio Andrey Oliveira wrote: > > > Thank you both for replying. > > It seems wsgi middleware fits better my needs. > > Regards. > > > Em segunda-feira, 5 de agosto de 2013 23h15min59s UTC-3, Marcio Andrey > Oliveira escreveu: >> >> Hi. >> >> In Java there is the concept of URL filter chain (implemented by one or >> more servlets). These filters may intercept requests to a specif URL or a >> bunch of them prior the request arrive to the controller(servlet) >> responsible to handle it. >> >> Is there such concept on web2py? >> >> How could I implement it? >> >> Thank you in advance. >> > -- --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
