Patch #33752

Uploading big files

Added by Karel Pičman 9 months ago. Updated 12 days ago.

Status:NewStart date:
Priority:NormalDue date:
Assignee:-% Done:


Target version:5.0.0


Uploading of a file bigger than available RAM fails with no memory error. I've found the reason in request.raw_post which is String and doesn't respond to :read. Consequently, the whole file is read into memory. The attached patch simply replaces raw_post with body which is type of StringIO that provides read method.

big_files_upload.diff Magnifier (594 Bytes) Karel Pičman, 2020-07-20 08:54

attachments_test.rb.patch Magnifier (1.22 KB) Pavel Rosický, 2020-07-20 23:57

file_size.diff Magnifier (1.16 KB) Karel Pičman, 2020-07-21 09:37

10-patches.rb.patch Magnifier (621 Bytes) Pavel Rosický, 2020-08-24 12:16


#1 Updated by Go MAEDA 9 months ago

Redmine originally used request.body, but changed to use request.raw_post in r9652 in order to fix an error regarding fastcgi (#10832). The attached big_files_upload.diff reverts r9652.

I think the patch can be merged to the core if the patch works fine with fastcgi.

#2 Updated by Pavel Rosický 9 months ago

in my opinion, the fix in #10832 is wrong. It breaks the concept of streaming file uploads

however, the proposed patch breaks FCGI. I've attached a test case.

unlike other request handlers, CGI uses a rewindable input, that doesn't support the #size method. In theory, the only way how to determine the file size is to read the content first. The content should be streamed into a tempfile not into a memory.

the second option is to rely on the CONTENT-LENGTH header, but it might not be accurate or it could be faked.

after some investigation, I found that Rails actually relies on the header

this means that FCGI is currently broken if an invalid CONTENT-LENGTH is provided. Note that most web-browsers and curl do send this header by default.

I'm wondering why anyone wants to use FCGI these days, they're definitely better options. We should try to fix it if possible, but the original patch #10832 broke other webservers that behave correctly.

#3 Updated by Karel Pičman 9 months ago

I think that the problem with the size can be solved as suggested by Pavel by getting the size after data are stored into the filesystem. See the patch.

#4 Updated by Go MAEDA 9 months ago

  • Target version set to Candidate for next minor release

#5 Updated by Go MAEDA 8 months ago

A test is broken after applying big_files_upload.diff and file_size.diff.

Redmine::ApiTest::AttachmentsTest#test_POST_/uploads.xml_should_return_errors_if_file_is_too_big [test/integration/api_test/attachments_test.rb:207]:
Expected response to be a <422: Unprocessable Entity>, but was a <201: Created>
Response body: <?xml version="1.0" encoding="UTF-8"?><upload><id>24</id><token>24.1d1801f753ccd9fa57966c46f360585caf83337a394a5f238d4e4e7d6005788d</token></upload>.
Expected: 422
  Actual: 201

bin/rails test test/integration/api_test/attachments_test.rb:204

#6 Updated by Pavel Rosický 8 months ago

there're validations for size before the file is actually uploaded.

let's choose a simpler approach. These patches should be commited:

it passes all tests.

#7 Updated by Pavel Rosický 15 days ago

@Go MAEDA may I ask for a review? it's a simple change.

#8 Updated by Go MAEDA 12 days ago

  • Target version changed from Candidate for next minor release to 5.0.0

Also available in: Atom PDF