ID 552197 - Large requests from the Flix Client can produce a 414 HTTP error

Problem summary:

Large requests from the Flix Client can produce a 414 HTTP error

Customer reported version:
Flix 6.6.1

Customer reported platform:

N/A

Steps to reproduce:
1) Reverse proxy Flix behind an AWS Load Balancer, or similar.
2) Create a Sequence Revision and batch import a large number of files.
3) Observe the 414 HTTP error in the client log.

Expected behavior:
If a request is too large, Flix should automatically retry the request in smaller batches.

Actual behavior:
Flix returns a generic HTTP error to the user and the batch import fails.

Workaround:
Manually uploading in smaller batches should allow the import(s) to be successful.

Reproduced by Development team in:
Flix 6.6.1