Sorry for the late reply, I have been swapped with work lately. I think I made some progress today, at least I think I found the culprit
On Tue, Sep 16, 2008 at 9:32 PM, Jorge Vargas <[EMAIL PROTECTED]> wrote: > > A little off topic, since I'm forced to have this mod_proxy, wouldn't > a better setup be to eliminate mod_wsgi, and just have their main > mod_proxy send requests to a paster serve ? I went for this setup so right now I have the same code running from two deployments. So having mod_proxy -> paster serve is giving exactly the same 302 headers error. Which means the bad header is being generated by paste.auth. With this I can confirm Graham's theory that mod_wsgi and apache by extend are just passing along what paste generated. For someone reading from paste-users mailing list here is the full thread http://groups.google.com/group/modwsgi/browse_thread/thread/16043503d522d45d/e0904f844aa125f2?#e0904f844aa125f _______________________________________________ Paste-users mailing list [email protected] http://webwareforpython.org/cgi-bin/mailman/listinfo/paste-users
