On Jul 29, 10:30 am, Malcolm Tredinnick <[EMAIL PROTECTED]>
wrote:
> On Sat, 2007-07-28 at 23:20 +0000, Graham Dumpleton wrote:
>
> [...]
>
> > FWIW, I know I said that SCRIPT_NAME can't be calculated in
> > mod_python. Well, that isn't strictly true.
>
> > If you are using mod_python 3.3.1 and have used the Location directive
> > then it is probably possible by using req.hlist.location.
>
> > I didn't mention this before because the fact it doesn't work with
> > older versions of mod_python nor when Location is not being used sort
> > of limits its usefulness. Didn't seem to make sense to therefore
> > depend on it.
>
> Aah.. thanks. That provides the explanation to resolve a note I made on
> Thursday evening: "did mod_python change at some point? 3.3 is now
> returning SCRIPT_NAME?!"
>
> Should be able to accommodate that, I'm sure. Thanks, Graham. I'm not
> going mad after all.

Sorry, but you may be going mad after all, unless I am.

The change in mod_python 3.3 to allow access to the value of the
Location directive in which the PythonHandler directive was used,
doesn't in anyway change what the value of SCRIPT_NAME is as set by
Apache. I would thus expect SCRIPT_NAME to still be wrong in various
circumstances.

Am a bit busy at the moment, but when I get a chance I'll revisit this
issue of SCRIPT_NAME with mod_python and see if I can't work out some
half sensible guidelines as to how Apache works out what to set it to
and how we may be able to work out a correct value. As I suggest
though, such magic may only be an option with mod_python 3.3 and then
not always.

Graham


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to