unicorn Ruby/Rack server user+dev discussion/patches/pulls/bugs/help
 help / color / mirror / code / Atom feed
From: Eric Wong <normalperson@yhbt.net>
To: unicorn list <mongrel-unicorn@rubyforge.org>
Subject: Re: Request-URI Too Long from mongrel-unicorn
Date: Thu, 12 Apr 2012 08:18:31 +0000	[thread overview]
Message-ID: <20120412081831.GA968@dcvr.yhbt.net> (raw)
In-Reply-To: <20120412034546.GA19006@dcvr.yhbt.net>

Eric Wong <normalperson@yhbt.net> wrote:
> Lawrence Pit <lawrence.pit@gmail.com> wrote:
> > Should there be a limit at all in unicorn? Should it not be assumed
> > this is configured at the webserver level, like:
> > 
> > http://wiki.nginx.org/NginxHttpCoreModule#large_client_header_buffers
> 
> There should be a limit in unicorn, it's cheap to enforce and there
> could be corner cases (nginx bugs, internal security probes) where it's
> helpful.  The unicorn parser is also used by servers (Rainbows!) that
> expect untrusted/malicious clients without nginx to protect it.

On the other hand, the _granularity_ of limits may unnecessary.  There
is already a 112K limit on the overall header size (which IMHO is really
huge).  However, this 112K overall limit is tunable on Rainbows! because
Rainbows! is designed to handle hundreds/thousands of clients in one
process.
_______________________________________________
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

      reply	other threads:[~2012-04-12  8:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-11  8:07 Request-URI Too Long from mongrel-unicorn Nuo Yan
2012-04-11 20:30 ` Eric Wong
2012-04-11 21:44   ` Nuo Yan
2012-04-12  3:52     ` Eric Wong
2012-04-11 23:43   ` Lawrence Pit
2012-04-12  3:45     ` Eric Wong
2012-04-12  8:18       ` Eric Wong [this message]

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=20120412081831.GA968@dcvr.yhbt.net \
    --to=normalperson@yhbt.net \
    --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).