|
I have a Django app where all pages work except for 2: a page with lots of images and another page with a big image. When accessed, this pages yield a 504 within 30seconds to 1 minute. I am using Django - sorl , so I think the 504 comes from sorl processing the thumbnails on first access: http://stackoverflow.com/questions/11034214/django-sorl-thumbnail-crash-lots-of-large-images I tried setting the apache TimeOut to 800, but it did not work. I ran into a webfaction page that said the timeout is a global setting, hence, changing it from apache's httpd.conf would not work. Is there any other way to set the timeout? |
|
No, there is no other setting other than in your application. However timeout should not be effected by an image, the image is only 1 file and not the django code which actually renders the site, it is likely not a simple timeout issue, but something within code which is timing out. If you are serving static media as outlined here, than it will be served by nginx, and so the image size should not effect it at all. hm. I am serving it via a static app, as said in the link. I am getting "Premature end of script headers: wsgi.py..." on my logs. Any ideas on this? It is an issue in the code or Apache configuration, 'premature end of scrip headers' means the HTML headers were not formatted correctly, which is a vague error. You need to try to further isolate the problem by checking the view code on the server without Apache/mod_wsgi to see where the issue might be. You may submit a support ticket with the URLs which are timing out if you would like us to look directly. like I said I can't really figure out the issue, because most of the pages are working fine. It's not sorl, as you have pointed out, because other pages render the images correctly. I think I'll submit a support ticket. |
