From: Alex Stahl <astahl@...5.com>
Date: 2010-12-08T05:31:55+09:00
Subject: Re: HTTP POST request --> Ruby server

--=-o/PECNdkBqwgk5mvNtSh
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit

Hard to say then what else might be the problem... are you using a
framework or writing "a tiny web server" from the ground up?  If it's
the latter, you're definitely reinventing the wheel and, IMHO, on your
own, since that problem's already been solved in perfectly adequate
ways.  (If the former, look for forums specific to that framework).

If you don't need to write your own server, but instead just need to
serve content/handle requests, why not use Sinatra?
(http://www.sinatrarb.com/).  If you must write your own server, then
perhaps run a packet sniffer on the server-side to see what it's
receiving, then work your way up the stack to see what ruby actually
receives.



________________________________________________________________________

Alex Stahl | Sr. Quality Engineer | hi5 Networks, Inc. | astahl@hi5.com
|

On Tue, 2010-12-07 at 14:20 -0600, Chananya Freiman wrote:

> Alex Stahl wrote in post #966971:
> > Can't say I know a solution for you... but you might want to try using
> > Wireshark to check what's being sent.  FF dev tools, in my experience,
> > tend to be somewhat buggy and don't always accurately report what's
> > going on.  Wireshark will give you a much more exacting view as to
> > what's in the content-body of the POST request.
> >
> > Especially because this part sounds really odd and not at all reflective
> > of what's happening - "FireFox simply stops sending data" - FF doesn't
> > send a header, wait for a response, and then send the body, which is
> > what this implies.  Lest you somehow configured it to use HEAD instead
> > of POST.
> >
> >
> > ________________________________________________________________________
> 
> Well, it seems like everything is ok by what Wireshark sees, yet it 
> doesn't work.
> 
> I thought that maybe Ruby doesn't like printing whatever data it 
> received, for some reason, but just iterating over gets the thread 
> stuck.
> 
> This is just weird...
> 

--=-o/PECNdkBqwgk5mvNtSh--