Edit history

Summary

30sec or 30,000ms timeouts seem to be set in quite a few locations within the code, and setting most of these to 120s or 120000ms hasn't had any impact yet. If someone could pinpoint which of the dozens of entries is in need of changing so our clients can upload more than 40MB on an attachment, that would be wonderful.

Steps to reproduce

1. Followed https://gist.github.com/PaulMColeman/e7ef82e05035b24300d2ea1954527f10 mostly as it is the only documentation that seems up-to-date
2. Log in, create new community
3. Attempt to upload 35MB file, timeout popup happens 30sec into upload.
4. Attempt 3 more times until upload speeds permit transfer in under 30sec.
5. Change any one of about 70 hard-coded references to timeouts with a value of 30 or 30000 by setting them to 120s / 120000ms respectively
6. Rebuild, redeploy, retest and notice zero change.
7. Surrender after 2 hours of guessing.

Logs or screenshots (optional)

image

Summary

30sec or 30,000ms timeouts seem to be set in quite a few locations within the code, and setting most of these to 120s or 120000ms hasn't had any impact yet. If someone could pinpoint which of the dozens of entries is in need of changing so our clients can upload more than 40MB on an attachment, that would be wonderful.

Steps to reproduce

1. Followed https://gist.github.com/PaulMColeman/e7ef82e05035b24300d2ea1954527f10 mostly as it is the only documentation that seems up-to-date
2. Log in, create new community
3. Attempt to upload 35MB file, timeout popup happens 30sec into upload.
4. Attempt 3 more times until upload speeds permit transfer in under 30sec.
5. Change any one of about 70 hard-coded references to timeouts with a value of 30 or 30000 by setting them to 120s / 120000ms respectively
6. Rebuild, redeploy, retest and notice zero change.
7. Surrender after 2 hours of guessing.

Environment (optional)

No response

Logs or screenshots (optional)

image

Checks

• ☑ I searched for existing issues and didn't find a duplicate.