[Mongrel] clients hang on large PUTs to Mongrel::HttpHandler-based web service
rf at ufl.edu
Wed Jun 4 20:17:19 EDT 2008
Great! I'll check the content length - right now, it's looking to
be some sort of network (maybe firewall) issue. When I have
it figured out I will report back. But instrumenting the mongrel
handler I wrote shows that it's attempting to put out a reasonable
Unfortunately security on this system is difficult - I just got
sudo access to tcpdump... I started out as a sysadmin, but
man, they drive me crazy sometimes...
Did I say that mongrel rocks?
>> On Tue, Jun 3, 2008 at 8:16 PM, Zed A. Shaw <zedshaw at zedshaw.com> wrote:
>> Naw, it's the content length in the body of a PUT, I ask since I saw
>> int content_length
> Well, looking in the source I can't see where that's actually used to
> store the Content-Length header value. It actually seems to be dead.
> Instead you have this line in http_request.rb:
> content_length = @params[Const::CONTENT_LENGTH].to_i
> Which is kind of vague, but there's a good chance it's implemented as a
> 32-bit signed integer giving you a problem with a 4G content size. It
> should be converted to a Bignum on overflow, but a quick test would be
> to check the class of the content_length right after this line to see
> what it's getting.
More information about the Mongrel-users