{var%20f='http://v.t.sina.com.cn/share/share.php?appkey=1515056452',u=z||d.location,p=['&url=',e(u),'&title=',e(t||d.title),'&source=',e(r),'&sourceUrl=',e(l),'&content=',c||'gb2312','&pic=',e(p||'')].join('');function%20a(){if(!window.open([f,p].join(''),'mb',['toolbar=0,status=0,resizable=1,width=440,height=430,left=',(s.width-440)/2,',top=',(s.height-430)/2].join('')))u.href=[f,p].join('');};if(/Firefox/.test(navigator.userAgent))setTimeout(a,0);else%20a();})(screen,document,encodeURIComponent,'','','https://www.manongdao.com/data/attach/logo/logo.png', '推荐 We Are One 的问题《Logging with Apache 2.4, mod_wsgi and Django》','https://www.manongdao.com/q-1112028.html','页面编码gb2312|utf-8默认gb2312'));){kind=link}
Is there a way to configure the logging with mod_wsgi and Django without losing the request information, such as remote client IP or unique log ID AND without using environ['wsgi.errors']?
I have been trying out different logging configurations for different mod_wsgi modes. I have found out that in daemon mode there is an issue which causes some logging information (related to request context) to get lost (see this SO post). This should however work in embedded mode (only prefork MPM?) and environ['wsgi.errors']. Nevertheless, I think it is a bad idea to make my applications logging dependent on the mod_wsgi...
If there is currently no way around using environ['wsgi.errors'] variable, is there a drop-in replacement/wrapper for Django logging middleware that can be used?