On 16/01/18 10:46, Graham Dumpleton wrote: > The access log is updated by the Apache child worker process that for > daemon mode is proxying the connection to the actual process running > your application. In this case where the client drops the connection > before a complete response could be sent back by the child worker > process, Apache is overriding the original status code that may have > come from the WSGI application, to indicate a failure occurred. I > will need to go back and look at the Apache code but I am not sure I > can change the behaviour of how Apache works for this. As far as > Apache is conce
The reply looks incomplete. Interestingly, I am seeing these errors since I solved the problem described in "mod_wsgi and WebDAV" and I converted the service from mod_proxy to be integrated in a virtualenv. Mod_proxy gave a 200/206 when the client disconnected prematurely. I got scared when I started to see 500 because I interpreted it as a service failure. It is a "false alarm", nothing wrong is going on. Confusing and scaring. So here we have an example where the right status code is given: mod_proxy. Could be a simple starting point. Thanks for your time, Graham. Much appreciated. -- Jesús Cea Avión _/_/ _/_/_/ _/_/_/ [email protected] - http://www.jcea.es/ _/_/ _/_/ _/_/ _/_/ _/_/ Twitter: @jcea _/_/ _/_/ _/_/_/_/_/ jabber / xmpp:[email protected] _/_/ _/_/ _/_/ _/_/ _/_/ "Things are not so easy" _/_/ _/_/ _/_/ _/_/ _/_/ _/_/ "My name is Dump, Core Dump" _/_/_/ _/_/_/ _/_/ _/_/ "El amor es poner tu felicidad en la felicidad de otro" - Leibniz -- You received this message because you are subscribed to the Google Groups "modwsgi" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/modwsgi. For more options, visit https://groups.google.com/d/optout.
signature.asc
Description: OpenPGP digital signature
