From: Justin Giancola <justin.giancola@gmail.com>
To: unicorn list <mongrel-unicorn@rubyforge.org>
Subject: Re: large uploads
Date: Thu, 29 Sep 2011 16:58:19 -0400 [thread overview]
Message-ID: <CAGpLkJ7xtyePOhZ5_cD5MbohBUKY9YSp_8Gwznzj8=9O5W9gng@mail.gmail.com> (raw)
In-Reply-To: <CAOf2Z5vd3WJJ1iNhGc4wQYcFbC2xWYVsOdrO+gH3aKMt8DGSow@mail.gmail.com>
On Thu, Sep 29, 2011 at 4:05 PM, John Joseph Bachir <j@jjb.cc> wrote:
> Does NGINX have inherent behavior which buffers requests? (Eric's email
> seemed to suggest that).
Nginx always buffers the entire body of requests before calling the
upstream application. If the body exceeds client_body_buffer_size
Nginx will store it in a tempfile.
> Thanks for the responses! So, I've see this module:
> https://github.com/vkholodkov/nginx-upload-module
The upload module works a little differently. It allows you to
configure specific upload endpoints that Nginx will preprocess. Rather
than forwarding the entire request body to the upstream application,
Nginx will parse the multipart/form-data encoded files, store them in
tempfiles, and forward only the paths of the tempfiles to the upstream
application.
Justin
_______________________________________________
Unicorn mailing list - mongrel-unicorn@rubyforge.org
http://rubyforge.org/mailman/listinfo/mongrel-unicorn
Do not quote signatures (like this one) or top post when replying
next prev parent reply other threads:[~2011-09-29 20:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-29 18:28 large uploads John Joseph Bachir
2011-09-29 18:47 ` Eric Wong
2011-09-29 20:05 ` John Joseph Bachir
2011-09-29 20:54 ` Eric Wong
2011-10-01 3:39 ` John Joseph Bachir
2011-10-01 4:06 ` Eric Wong
2011-09-29 20:58 ` Justin Giancola [this message]
2011-09-29 18:48 ` cliftonk
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://yhbt.net/unicorn/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAGpLkJ7xtyePOhZ5_cD5MbohBUKY9YSp_8Gwznzj8=9O5W9gng@mail.gmail.com' \
--to=justin.giancola@gmail.com \
--cc=mongrel-unicorn@rubyforge.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://yhbt.net/unicorn.git/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).