Hi,
[moving my StackOverflow question to the mailing list per Graham
Dumpleton's suggestion; note his reply there:
http://stackoverflow.com/questions/2244244/
]
My Django app, deployed using Django's standard WSGIHandler,
authenticates users via form login on the Django side. So to Apache,
the user is anonymous, making for an unsatisfying access log.
I want to pass the username back through the WSGI wrapper to Apache
after handling the request, so that it appears in the Apache access
log.
Graham's suggestion involves using apswigpy and configuring mod_wsgi
to pass the Apache request object in as a Python CObject. Even then,
he says it will only work in embedded mode.
Some follow-up questions:
1) the apswigpy page says it was abandoned in 2007 due to lack of
interest, and was then “very much a work in progress”. This sounds a
tad risky. Graham being the author of both mod_wsgi and apswigpy, I
don't suppose I should hope that anyone else here knows a better
way? :)
2) is the limitation to embedded mode just a reference to mod_wsgi's
(or apswigpy's) current implementation, or is it inherent in the
Apache invocation model? I.e. will this *continue* to be possible only
in embedded mode?
3) is there a reason why that functionality in apswigpy isn't/
shouldn't be merged into mod_wsgi as an optional extra? Because
mod_wsgi wants to stick strictly to implementing only the WSGI spec?
Regards,
- Gulli
--
You received this message because you are subscribed to the Google Groups
"modwsgi" 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/modwsgi?hl=en.
