Details
Description
Content Hosting uses int for file size (content length) which imposes a 2G limit on files.
Adjust this and related code to use long, to allow files > 2G.
This will only work for file system storage where files can be streamed in and out - files stored in the db have a 2G limit because of the limit of the size of a byte array and jvm memory constraints.
Gliffy Diagrams
Zeplin
Attachments
Issue Links
- depends on
-
SAK-39261 Do not read resource body into memory when deleting file
-
- CLOSED
-
-
SAK-39317 archiveResource uses byte array instead of stream to archive content
-
- CLOSED
-
- is related to
-
SAK-10822 WebDAV downloads cause OutOfMemoryError on server
-
- CLOSED
-
-
SAK-16492 Checking content length on uploads is not necessary
-
- CLOSED
-
-
SAK-16806 Uploading a file through Resources tool loads the body into memory
-
- CLOSED
-
-
SAK-39673 Support partial requests in access servlet
-
- CLOSED
-
- relates to
-
SAK-16844 content.upload.max=2048 (or greater) will prevent "upload all" from uploading any file
-
- CLOSED
-
-
SAK-16838 Uploading a file through Attachments helper loads the body into memory
-
- CLOSED
-
-
SAK-18229 Adjust code in preparation for allowing content size > 2G
-
- CLOSED
-
-
SAK-39666 Add methods to stream attachments rather than load into memory
-
- CLOSED
-