[
http://issues.apache.org/jira/browse/MODPYTHON-128?page=comments#action_12370963
]
Graham Dumpleton commented on MODPYTHON-128:
--------------------------------------------
Put dunce cap on, stand in corner.
Naming is consistent now. Prefixes are never dropped. the FINFO_* and URI_*
constants are special as there is no equivalent in Apache and they are only
relevant to mod_python.
Thus, contains should therefore be:
mod_python.apache.APR_NOFILE
mod_python.apache.APR_REG
mod_python.apache.APR_DIR
mod_python.apache.APR_CHR
mod_python.apache.APR_BLK
mod_python.apache.APR_PIPE
mod_python.apache.APR_LNK
mod_python.apache.APR_SOCK
mod_python.apache.APR_UNKFILE
> Have assigning req.filename automatically update req.finfo.
> -----------------------------------------------------------
>
> Key: MODPYTHON-128
> URL: http://issues.apache.org/jira/browse/MODPYTHON-128
> Project: mod_python
> Type: Improvement
> Components: core
> Versions: 3.3
> Reporter: Graham Dumpleton
>
> Although it is possible to assign a new value to "req.filename", it is not
> possible to update "req.finfo" based on the new filename.
> Suggest that if "req.filename" is assigned a new value, that apr_stat() be
> automatically called to update "req.finfo". Ie., internally mod_python would
> do something like:
> apr_stat(&r->finfo, r->filename, APR_FINFO_MIN, r->pool);
> I believe that mod_perl supports a similar feature, but would need to confirm
> this.
> Related to "req.filename", the "req.canonical_filename" should also be
> writable as when changing "req.filename" the latter should also by rights be
> updated as well.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
