Re: Django **not responding** when DEBUG = FALSE - No error raised / Apache HTTPError issue (?)

2015-01-04 Thread Paul Antropius
Okay, it was just an old and obsolete custom security with my wikitools module, that prevents the code to access an external website under debug mode... It thus returned a 404 code, and the wikitools api was forcing the connection with this 5 seconds step pattern... Let's rock ! :-) BTW : I

Re: Django **not responding** when DEBUG = FALSE - No error raised / Apache HTTPError issue (?)

2015-01-04 Thread Paul Antropius
Le dimanche 4 janvier 2015 00:16:33 UTC+1, Mike Dewhirst a écrit : > > On 3/01/2015 10:19 PM, Paul Antropius wrote: > > Good morning, > > > > The production server sends absolutely **no response** when DEBUG is set > > to FALSE. > > Browser still waits fo

Django **not responding** when DEBUG = FALSE - No error raised / Apache HTTPError issue (?)

2015-01-03 Thread Paul Antropius
Good morning, The production server sends absolutely **no response** when DEBUG is set to FALSE. Browser still waits for a response : no error (neither 404, nor 500) is raised. Minutes later, it ends up with a 503 error. Apache error log reads : HTTPError: HTTP Error 404: Not Found trying