From: Eric Wong <normalperson@yhbt.net>
To: Nuo Yan <yan.nuo@gmail.com>
Cc: unicorn list <mongrel-unicorn@rubyforge.org>
Subject: Re: Request-URI Too Long from mongrel-unicorn
Date: Wed, 11 Apr 2012 20:30:54 +0000 [thread overview]
Message-ID: <20120411203054.GB22267@dcvr.yhbt.net> (raw)
In-Reply-To: <CB935F19-72B8-4EC2-8A1D-5084B37C09F2@gmail.com>
Nuo Yan <yan.nuo@gmail.com> wrote:
> In my understanding, the mongrel request uri limit is 12k.
Correct, that's the entire REQUEST_URI, though:
REQUEST_PATH?QUERY_STRING#FRAGMENT
> My request uri is certainly not that long (about 1445 bytes), but for
> some reason I'm getting 414 Request-URI Too Long from the server.
Perhaps one of your URI components (perhaps REQUEST_PATH) is too long?
The current limits are as follows (in ext/unicorn_http/global_variables.h)
DEF_MAX_LENGTH(REQUEST_URI, 1024 * 12);
DEF_MAX_LENGTH(FRAGMENT, 1024); /* Don't know if this length is specified somewhere or not */
DEF_MAX_LENGTH(REQUEST_PATH, 1024);
DEF_MAX_LENGTH(QUERY_STRING, (1024 * 10));
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.
_______________________________________________
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:[~2012-04-11 21: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 [this message]
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
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=20120411203054.GB22267@dcvr.yhbt.net \
--to=normalperson@yhbt.net \
--cc=mongrel-unicorn@rubyforge.org \
--cc=yan.nuo@gmail.com \
/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).