Use the first logging middleware sample in: http://code.google.com/p/modwsgi/wiki/DebuggingTechniques#Tracking_Request_and_Response
to capture the actual response status and headers in Apache error log to confirm what Quixote is actually returning. Also look at your Apache installation to see if if defines any ErrorDocument directives related to the status codes you are trying to return. BTW, mod_wsgi 2.1 is quite old now. Graham 2009/8/22 Hamish Lawson <hamish.law...@gmail.com>: > > We have a Quixote application that is intended to return a 403 status > code under certain circumstances. While this is what happens on our > development web server, on our production web server we get a 200 code > instead of the expected 402. Since one of the main differences between > the production and development servers is that the production one is > using mod_wsgi, is it possible that mod_wsgi might be somehow changing > the issued 403 code to a 200? Here are fuller descriptions of the > respective setups: > > PRODUCTION > > Apache 2.2.11 > mod_wsgi 2.1 > Quixote 2.4 > Python 2.5.2 > Solaris 10 > > DEVELOPMENT > > Apache 1.3.27 > SCGI 1.12 > Quixote 2.4 > Python 2.4.2 > Solaris 10 > > Thanks, > Hamish Lawson > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "modwsgi" group. To post to this group, send email to modwsgi@googlegroups.com To unsubscribe from this group, send email to modwsgi+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/modwsgi?hl=en -~----------~----~----~----~------~----~------~--~---
