Comment 2 for bug 1703856

My concern with just bumping the uwsgi timeout is that is nothing in this bug that points to why that fixes it. When we bumped it from the default of 4 secs to 30 that was supposed to be an overly conservative value because we were seeing socket timeouts while uwsgi was waiting for chunked data on the wire at high load situations.

I'm afraid just doing that without classifying the underlying cause of uwsgi not responding (or just closing the socket, its not clear from anything here) which causes the apache proxy to return 502 will mask a real bug somewhere else. My other concern with just bumping the timeout is you're only testing with a 10GB what if you want to upload a 200GB image file, or a 2TB image file?