[web2py] Re: mod_wsgi errors -- dead in the water

2015-03-30 Thread weheh
Thanks, Brian. My page does have a lot of ajax calls. The problem seems to be that some of my css files aren't coming through. Firebug says they're being delivered as text/plain instead of text/css. Consequently, the page load incorrectly and users probably bail, causing the IO Error in mod_wsgi

[web2py] Re: mod_wsgi errors -- dead in the water

2015-03-30 Thread Brian M
I also run with the apache + mod_wsgi combo on windows and see this error a lot. Never have been able to figure out a cause other than the client disconnecting like niphlod mentioned. If it is something else that can actually be fixed I'd love to know. Not sure if it matters but I see it predom

[web2py] Re: mod_wsgi errors -- dead in the water

2015-03-30 Thread weheh
Config? Windows 7. Apache 2.X. mod_wsgi. python 2.7.x. The modwsgi config is as follows: DocumentRoot "C:/web2py/applications" ServerName www.yakitome.com SSLCipherSuite AES128+EECDH:AES128+EDH SSLProtocol All -SSLv2 -SSLv3 SSLHonorCipherOrder On Header always set Strict-Transport-Se

[web2py] Re: mod_wsgi errors -- dead in the water

2015-03-30 Thread Niphlod
what config are you using ? failed to write data is usually meaning that the client terminated the socket before apache being able to stream the response back to it. kinda of "close the browser in the middle of a download". On Tuesday, March 31, 2015 at 12:33:14 AM UTC+2, weheh wrote: > > On a W