Fix: Re: [modwsgi] Error 500 with no logs when the client closes early

On 16/01/18 18:13, Jesus Cea wrote: > Thanks for your time, Graham. Much appreciated. Reading source code, I see things I don't understand and could be the issue: When a request is processed, if it preemptively marked as "error 500". This code will be changed to the right result code when the

Re: [modwsgi] Error 500 with no logs when the client closes early

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

Re: [modwsgi] mod_wsgi and WebDAV

On 16/01/18 13:58, Graham Dumpleton wrote: > Thanks for letting me know. > > Not sure why it seems I never responded at the time. I suspect I may have > been overseas start of Dec 2015, but still no excuse. :-) I am always amazed by your responses in this group. Getting the usually "bull-eyed"

Re: [modwsgi] mod_wsgi and WebDAV

Thanks for letting me know. Not sure why it seems I never responded at the time. I suspect I may have been overseas start of Dec 2015, but still no excuse. :-) Graham > On 15 Jan 2018, at 1:29 am, Jesus Cea wrote: > > On 03/12/15 16:40, Jesus Cea wrote: >> I have an Apache

[modwsgi] mod_wsgi providing cve-search

Hi, guys! So, it's my first time using mod_wsgi, actually, is the first time that I want server a python application. I want host the application cve-search [0] using apache and mod_wsgi. The cve-search's web interface use Flask [1] and looking at Flask docs there is a section talk about wsgi