Comment 6 for bug 1041880

So here's my current findings.

Since the OAuth timestamp was fixed the files of larger size were enabled to go through. However the updown server has only 50 seconds to reply before haproxy kicks in and sends 504 response.

During my two latest test of 300Mb upload the files were uploaded properly but the request failed with 502 Proxy error and 504 Gateway Timeout. In both cases the files were handled properly by updown but the client did not know that.

updown needs to spool the file completely first before compressing it, getting the hashes and sending it to storage and this process may take much more than 50 seconds.