On 26 May 2011 23:38, Frederik Vogelsang <[email protected]> wrote: >> There is a back door way of doing what you want but it entails needing >> to writing a C extension or use some Python SWIG bindings which exist. >> I am not sure though whether I will continue to keep the backdoor >> though as no one has expressed any real interest in developing the >> idea. > *sigh*, this does not look like a clean solution. I hope I gave you a > proper use case scenario for this kind of setup, maybe you'll consider > an official way of modifying the remote user (just like mod_python).
The problem is that there are so many different little extensions like this that people may want. The only one I have added inbuilt support for up to now is getting access to ssl optional functions for getting ssl variable access as that fitted in cleanly. Mostly anything else is never going to be able to be done in a clean way because of the simplistic API for that function and I don't want to create a growing mess of hacked in add ons. The mod_python code became a mess and unmanageable because of that. As such, the point of apswigpy was to create an official way for people who want to do not common things to do it, by providing a Python binding to the internal Apache request object. It was as clean as one could get, but seems people are turned off by the bulk of the API in that it lets them do huge amounts of stuff when they only wanted to solve one specific task. The only other option to apswigpy which does not result in changes to mod_wsgi is to write a C extension module instead. This is how access was granted to the ssl variable stuff initially so there already is a example which can be easily adapted to do it. Anyway, since this is about the third time that there has been a request for a way to change REMOTE_USER I'll give some thought to how one could do it. Also option to suggestions on how you think you would like to see it done, remembering you can't change the API to the check_password function(). Graham -- 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.
