On Tue, Jul 10, 2007 at 04:25:17PM -0400, Marty Alchin wrote: > > On 7/10/07, Forest Bond <[EMAIL PROTECTED]> wrote: > > All of this could be fixed by simply changing ModPythonRequest > > (django/core/handlers/modpython.py) to use req.path_info instead of req.uri. > > Is there any reason not to do that (aside from breaking backwards > > compatibility)? > > I'm certainly no expert in this area, but keep in mind that mod_python > is just one available option for deploying Django. There would have to > be some equivalent in the other situations, such as FastCGI, in order > for this to be taken seriously.
Is this kind of change relevant for all of the other methods? I have not used any of the others. Certainly, if a change like this is made, the other handlers would need to be updated for consistency. I agree with you there. If there was some way to tell apache/mod_python to pass the URL sans the prefix in to django, I would simply do that. I have not been able to find any such thing. But really, the prefix is a deployment detail that I should be able to make my application agnostic to. I don't have to include my domain name in my urls.py, why should I have to include a prefix? Maybe this behavior could be determined by something in settings.py. -Forest
signature.asc
Description: Digital signature
