From: Richard Penwell <almightylinuxgod@me.com>
To: Eric Wong <normalperson@yhbt.net>
Cc: unicorn list <mongrel-unicorn@rubyforge.org>
Subject: Re: Problem with x-www-form-urlencoded
Date: Thu, 15 Jul 2010 18:30:35 -0400 [thread overview]
Message-ID: <6A2DBCB2-916B-49DD-A513-360494AAA73E@me.com> (raw)
In-Reply-To: <20100715221402.GA31045@dcvr.yhbt.net>
So I discovered this was a problem whereby request.body.to_s behaves differently. I wonder if TeeStream should define to_s as an alias for read?
Sent from my iPhone
On Jul 15, 2010, at 6:14 PM, Eric Wong <normalperson@yhbt.net> wrote:
> Richard Penwell <almightylinuxgod@me.com> wrote:
>> Howdy all,
>
>> I'm having a strange issue after moving from Thin to Unicon. One of
>> the form values being posted is not showing up in our request, below
>> you can see a Rails log entry and notice that there is no parameter
>> 'messageID' but it shows in the
>> 'action_dispatch.request.request_parameters' collection.
>
> Hi Richard, Which versions of Rails and Rack are you using?
>
> There's a chance Thin and Unicorn could be loading different
> versions of Rack and we might be hitting a bug in one version
> of Rack.
>
>> Has anyone else seen this, and is there a solution?
>
> I haven't seen nor looked into this myself, but I've heard some talk of
> multipart oddness in the Rack mailing list
>
> --
> Eric Wong
_______________________________________________
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:[~2010-07-15 22:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-15 20:46 Problem with x-www-form-urlencoded Richard Penwell
2010-07-15 22:14 ` Eric Wong
2010-07-15 22:30 ` Richard Penwell [this message]
2010-07-15 22:40 ` Eric Wong
2010-07-15 23:49 ` Richard Penwell
2010-07-16 7:54 ` Eric Wong
2010-07-16 13:17 ` Richard Penwell
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=6A2DBCB2-916B-49DD-A513-360494AAA73E@me.com \
--to=almightylinuxgod@me.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).