|
If you were logged in you would be able to see more operations.
|
|
|
| Resolution Date: |
08/May/06 06:15 PM
|
|
Add new member function to request object called "add_output_filter()". This would be a wrapper around the function "ap_add_output_filter()" and allow previously defined filters to be attached to the current request such that output can be filtered through them. For example:
req.add_output_filter("INCLUDES")
It would probably be necessary for any such call to be done prior to the first output being generated from the request handler.
In addition to this member function, it may be necessary to also provide another member function called something like "req.add_python_output_filter()". This would be called something like:
req.add_python_output_filter("module_name::filter_name",path)
Ie., like "req.add_handler()" but no first argument for phase.
This method would allow a specific Python filter handler function to be specified. This would be equivalent to using the PythonOutputFilter directive to first name a mod_python based filter handler function and then adding it as an output filter.
# Main Apache config.
PythonOutputFilter module_name::filter_name MYFILTER
# Handler code.
req.add_output_filter("MYFILTER")
Note that the PythonOutputFilter directive can only be used in the main Apache configuration file, it cannot be used in a .htaccess file. Whether it could be made to work in a .htaccess file in some way needs to be investigated. In mod_perl their equivlent seems to allow it.
|
|
Description
|
Add new member function to request object called "add_output_filter()". This would be a wrapper around the function "ap_add_output_filter()" and allow previously defined filters to be attached to the current request such that output can be filtered through them. For example:
req.add_output_filter("INCLUDES")
It would probably be necessary for any such call to be done prior to the first output being generated from the request handler.
In addition to this member function, it may be necessary to also provide another member function called something like "req.add_python_output_filter()". This would be called something like:
req.add_python_output_filter("module_name::filter_name",path)
Ie., like "req.add_handler()" but no first argument for phase.
This method would allow a specific Python filter handler function to be specified. This would be equivalent to using the PythonOutputFilter directive to first name a mod_python based filter handler function and then adding it as an output filter.
# Main Apache config.
PythonOutputFilter module_name::filter_name MYFILTER
# Handler code.
req.add_output_filter("MYFILTER")
Note that the PythonOutputFilter directive can only be used in the main Apache configuration file, it cannot be used in a .htaccess file. Whether it could be made to work in a .htaccess file in some way needs to be investigated. In mod_perl their equivlent seems to allow it.
|
Show » |
| Repository |
Revision |
Date |
User |
Message |
| ASF |
#405290 |
Tue May 09 03:30:57 UTC 2006 |
grahamd |
Old variable definition not removed and was hiding function parameter. If
variable definition attained a non null value, code could also crash. In
worst case, if neither handler or filter specified, result would have been
value of PythonInterpPerDirective setting. The latter shouldn't in practice
occur but cater for it anyway. (MODPYTHON-103)
|
| Files Changed |
MODIFY
/httpd/mod_python/trunk/src/mod_python.c
|
|
New Feature
Closed
Major
Implement req.add_output_filter().
