Changes between Version 1 and Version 2 of RequestFilters

Timestamp:

Jun 25, 2008, 10:32:15 PM (16 years ago)

Author:

cmlenz

Comment:

--

RequestFilters

@@ -51 +51 @@
 This implementation removes a number of the default filters. You could also add any custom filters you may have, etc.
 
-Note that the ordering of request filters is quite important. For example, if you insert your custom filter before the `error_filter`, an exception raised in your filter function will not result in a friendly error page, but rather see the exception propagated all the way up. If you insert your filter before the `template_filter`, you will not get a Genshi stream as return value of the next function in the chain, but rather the rendered text.
+Note that the ordering of request filters is quite important. For example, if you insert your custom filter before the `error_filter`, an exception raised in your filter function will not result in a friendly error page, but rather result in the exception being propagated all the way up to the WSGI gateway. If you insert your filter before the `template_filter`, you will not get a Genshi stream as return value of the next function in the chain, but rather the rendered text.
 
-Generally it makes the most sense to add custom filters close to the end of the list.
+When in doubt, add custom filters close to the end of the list.
 
 == When to Use Request Filters ==