unicorn Ruby/Rack server user+dev discussion/patches/pulls/bugs/help
 help / color / mirror / code / Atom feed
From: Nuo Yan <yan.nuo@gmail.com>
To: Eric Wong <normalperson@yhbt.net>
Cc: unicorn list <mongrel-unicorn@rubyforge.org>
Subject: Re: Request-URI Too Long from mongrel-unicorn
Date: Wed, 11 Apr 2012 14:44:09 -0700	[thread overview]
Message-ID: <DA54B80C-E3A4-4D8C-B593-5D10B9E8E83C@gmail.com> (raw)
In-Reply-To: <20120411203054.GB22267@dcvr.yhbt.net>

Hi Eric,

On Apr 11, 2012, at 1:30 PM, Eric Wong wrote:
> 
> I will consider upping REQUEST_PATH to 4096 (and REQUEST_URI to 15K)
> since 4096 is a common filesystem PATH_MAX on modern systems.
> 
> Would anybody object to this?  Given we already allow huge headers and
> Ruby uses quite a bit of memory, I don't think a potential extra 3K
> will negatively impact anybody.

Lately I figured REQUEST_PATH should probably be the reason as well. It would be great if you bump that up to 4096 - so that we could continue to use released versions instead of having to patch on our own. 

4k makes sense to me. When do you think you can cut a gem on this?

Also, what do you think about making these values configurable in the conf file? I understand these were hard coded by design to protect the server. However, I think it would be nice if it defaults to these small values and can be configured flexibly. 

Thanks a lot,
Nuo

_______________________________________________
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-11 22:07 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 [this message]
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

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=DA54B80C-E3A4-4D8C-B593-5D10B9E8E83C@gmail.com \
    --to=yan.nuo@gmail.com \
    --cc=mongrel-unicorn@rubyforge.org \
    --cc=normalperson@yhbt.net \
    /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).