Django and fastcgi upstream application timeout

[Ola]

I have been trying to compare django application deployment on nginx and apache and what I came across is an issue with fastcgi upstream application timeout. Basically the following configs return as stated:

location / {
  ...
  fastcgi_read_timeout 60
}

504 Gateway Time-out 1m

FastCGIExternalServer "/path/to/myapp.fcgi" 0.0.0.0:4080 -idle-timeout 60

500 Internal Server Error 1m

With my custom handler500 ('django.views.defaults.server_error') I am catching that as standards error, that is not really what I feel should happen. Definitely 504 Gateway Timeout is more intuitive. Although, I have no way of catching 504 with default django HttpResponse. Is there any plan to help developers to handle it better and unify it?

[Tim Graham]

I don't think so. In fact, FastCGI support has been deprecated in Django 1.7 and will be removed in Django 1.9.

Also as this seems more of a usage question, it's more appropriate to ask using the resources found in TicketClosingReasons/UseSupportChannels.