Opened 12 years ago
Last modified 12 years ago
#240 closed defect (FIXED)
Provide facility for configuring application-required middleware
|Reported by:||nyergler||Owned by:||nyergler|
Some things, like CSRF protection (`#361 </issues/361>`_), benefit from the ability to uniformly call helpers before and after a request is processed by the view. In the case of CSRF, we want to confirm that the token matches before processing the view, and make sure the token is set before delivering the response. Unlike WSGI middleware, this sort of wrapping is an integral part of the application.
Change History (4)
comment:1 by , 12 years ago
|Status:||New → In Progress|
comment:2 by , 12 years ago
|Status:||In Progress → Closed|
Looks great to me. I suspect as for "configuration' of this middleware our current config files suffice... maybe we could create a standard for sections of the application for various middleware configs, but otherwise looks great. Merged, and closed!
comment:3 by , 12 years ago
|Component:||Infrastructure → Programming|
comment:3 by , 11 years ago
The original url for this bug was http://bugs.foocorp.net/issues/569 .
Note: See TracTickets for help on using tickets.