Request logging goes missing in SSL virtual host when using daemon mode.

[GoogleCodeExporter]

When WSGI application is delegated to daemon mode and there is a port 80 
virtual host with WSGIDaemonProcess defined within the virtual host, but also 
another virtual host for same server name using a different port, eg., 443, but 
using the daemon process defined in port 80 virtual host, and each has an 
ErrorLog directive which refers to the same log file, error messages logged 
against the request will go missing for all but the first virtual host with 
same ErrorLog, eg., in this case errors for HTTPS requests against port 443 
will go missing.

The obvious manifestation of this is in this example is that when making HTTPS 
request (but not HTTP request) if there is a run time exception in the WSGI 
application when WSGI script being loaded, or when the request is being 
handled, the traceback and details of that error will not appear in the log 
file and only evidence of problem would be the HTTP 500 response. Thus there is 
a loss of information and hard to debug what has gone wrong.

This issue may manifest in other variations when using daemon mode and multiple 
virtual hosts for same server name.

This issue is fixed in r1598 of trunk for mod_wsgi 4.0. The fix will be back 
ported to 3.X and new 3.X release made. The issue does not affect 2.X.

Original issue reported on code.google.com by Graham.Dumpleton@gmail.com on 5 Jul 2010 at 12:28

[GoogleCodeExporter]

Original comment by Graham.Dumpleton@gmail.com on 12 Jul 2010 at 2:01

• Added labels: Milestone-Release3.3
• Removed labels: Milestone-Release4.0

[GoogleCodeExporter]

Back ported to mod_wsgi 3.X branch for 3.3 in revision 1599.

Original comment by Graham.Dumpleton@gmail.com on 12 Jul 2010 at 2:02

[GoogleCodeExporter]

Version 3.3 has been released.

Original comment by Graham.Dumpleton@gmail.com on 31 Jul 2010 at 10:39

• Changed state: Fixed