Reputation
Top tag
Next privilege 200 Rep.
See reduced ads
Badges
6
Newest
 Scholar
Impact
~3k people reached

  • 0 posts edited
  • 1 helpful flag
  • 5 votes cast
Sep
29
awarded  Scholar
Sep
29
accepted Nginx client_body_in_file_only for file upload performance
Sep
29
comment Nginx client_body_in_file_only for file upload performance
I believe the idea is to no not tie up application processes by having nginx buffer the entire request to disk and then passing the request to the application process. I was confused that in either case disk buffering was happening, but your answer is helpful in explaining that the files are not deleted when you set it to on, which enables this approach. I should also add that in an nginx/unicorn or similar environment, this approach is moot because application processes are not actually blocked. therailsway.com/2009/4/23/uploading-files
Aug
27
awarded  Popular Question
Oct
27
awarded  Student
Oct
16
comment Nginx client_body_in_file_only for file upload performance
Yes, I did. The answer explains the message written to the log, but not explain the effect client_body_in_file_only on; on uploads - or even mention that directive.
Oct
15
awarded  Citizen Patrol
Oct
13
comment Nginx client_body_in_file_only for file upload performance
This is not a duplicate. The question you linked to deals with client_body_buffer_size but does not answer my question of the effect of client_body_in_file_only on; on uploads.
Oct
11
asked Nginx client_body_in_file_only for file upload performance
Dec
23
awarded  Teacher
Sep
18
answered Running Rails3 with force_ssl = true, with nginx, on AWS EC2 with SSL terminated by an ELB, setting up health check
Jan
25
awarded  Supporter