[ http://issues.apache.org/jira/browse/MODPYTHON-128?page=all ]

Graham Dumpleton updated MODPYTHON-128:

    Attachment: MP128_20060423_grahamd_1.diff

Here is one last attempt to get some sort of solution for this happening.

Have attached "MP128_20060423_grahamd_1.diff" containing a proposed patch to 
add a distinct req.update_finfo() function. When this function is called it 
will do an apr_stat() on the current value of req.filename and update req.finfo 
correspondingly. The result of the apr_stat() can be determined by consultation 
of req.finfo and specifically the req.finfo[FINFO_FILETYPE] attribute. It being 
APR_NOFILE if the stat failed.

> 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
>     Assignee: Graham Dumpleton
>  Attachments: MP128_20060423_grahamd_1.diff
> 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:
For more information on JIRA, see:

Reply via email to