Allan Saddi's projects blog

I merged all the Python 3.x-specific commits in ajp-wsgi-py3.0 into scgi-wsgi and surprisingly, it was painless and (seemingly) functional on the first try.

scgi-wsgi for Python 3.2 (Hg repo)

(Don't forget to clone scgi, threadpool and preforkserver as well.)

Really cool stuff. Though admittedly, most of my amazement comes from how easy it was to cherry-pick and merge specific revisions thanks to Mercurial.

Addendum: Oh yeah, I fixed ajp-wsgi-py3.0 so it compiles under Python 3.2. Even though the PyCapsule stuff was backported to Python 2.7, I won't be merging that change over. I still want the Python 2.x version to work with Python as old as 2.4.

It was brought to my attention that my trac sites were no longer authenticating the generic user I set up. Apparently, something I missed in my switch to SCGI...

But it's not scgi-wsgi's fault, really. I narrowed it down to mod_proxy_scgi (obviously, by the title of this entry!). mod_scgi works fine. mod_proxy_scgi does not seem to pass the HTTP Authorization header along. I'm currently looking around for flags/options to remedy this with no luck. A quick Google search revealed something similar, but not quite. Though that may address the SCRIPT_NAME/PATH_INFO issues I've seen... in a future version of Apache HTTPD.

I wish I had more time to figure out what was really going on. In the mean time, I will probably switch away from mod_proxy_scgi (to mod_scgi) where possible...