Mongrel users - Aug 2006 - BAD CLIENT, Invalid HTTP Format - Firefox, IE, etc..

I''m not sure what''s happening so I''ll try and explain
what I know.


I am getting the error "Thu Aug 17 20:01:57 MDT 2006: BAD CLIENT
(xx.xx.xx.xx): Invalid HTTP format, parsing fails."

I''m running mongrel 0.3.13.4 from gem source, and running on a Macbook
Pro.

I am running rails in development mode and if I switch to running
webrick, all requests come through as normal and return valid
responses.

So, the only problem I have is using a windows machine to access
portions of the site.  So far, I can consistently reproduce the
problem in Firefox 1.0.7.  I also can reproduce this in IE.  One
windows machine is a Parallels VM with a base, Win XP system.  The
other had Zonealarm firewall, but I have disabled that due to the
thread that mentioned Mcafee security center.

So, what are some ideas and is it possible that I am missing something
critical that I have overlooked?

Thanks for any help,


Steve Spigarelli

On Thu Aug 17, 2006 at 08:02:41PM -0600, Steve Spigarelli
wrote:
> I''m not sure what''s happening so I''ll try and
explain what I know.
> 
> 
> I am getting the error "Thu Aug 17 20:01:57 MDT 2006: BAD CLIENT
> (xx.xx.xx.xx): Invalid HTTP format, parsing fails."
it would be helpful to know what HTTP request is being sent. on windows this
util can tell you: http://www.analogx.com/files/pmoni.exe

or you could make mongrel spit the request to stderr..

Is there an easy configuration to do that, or should I modify the gem source?


On 8/17/06, carmen <_ at whats-your.name> wrote:
> On Thu Aug 17, 2006 at 08:02:41PM -0600, Steve Spigarelli wrote:
> > I''m not sure what''s happening so I''ll try
and explain what I know.
> >
> >
> > I am getting the error "Thu Aug 17 20:01:57 MDT 2006: BAD CLIENT
> > (xx.xx.xx.xx): Invalid HTTP format, parsing fails."
>
> it would be helpful to know what HTTP request is being sent. on windows
this util can tell you: http://www.analogx.com/files/pmoni.exe
>
> or you could make mongrel spit the request to stderr..
> _______________________________________________
> Mongrel-users mailing list
> Mongrel-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/mongrel-users
>

Looks like the request is coming in as:

delete /member/main/delete_favorite/12 HTTP/1.1\r\n ... standard
headers and content..


Any ideas?  I am sending "delete" as the method instead of get or post
but I might be doing something that really isn''t supported or that I
just don''t understand quite yet..  I think I''ll see what other
ways I
can find to do this.  I was trying to get a little more restian and I
thought Rails converted the delete method to a "post" but I guess
I''ll
have to work on this a little more.

Thanks for the help,

Steve

On 8/17/06, Steve Spigarelli <spig at spig.net>
wrote:
> Is there an easy configuration to do that, or should I modify the gem
source?
>
>
> On 8/17/06, carmen <_ at whats-your.name> wrote:
> > On Thu Aug 17, 2006 at 08:02:41PM -0600, Steve Spigarelli wrote:
> > > I''m not sure what''s happening so I''ll
try and explain what I know.
> > >
> > >
> > > I am getting the error "Thu Aug 17 20:01:57 MDT 2006: BAD
CLIENT
> > > (xx.xx.xx.xx): Invalid HTTP format, parsing fails."
> >
> > it would be helpful to know what HTTP request is being sent. on
windows this util can tell you: http://www.analogx.com/files/pmoni.exe
> >
> > or you could make mongrel spit the request to stderr..
> > _______________________________________________
> > Mongrel-users mailing list
> > Mongrel-users at rubyforge.org
> > http://rubyforge.org/mailman/listinfo/mongrel-users
> >
>

>From windows boxes I was having problems with link_to and the :method
=> ''delete''.  In my controller I was then checking for
request.delete?. I have changed this back to :method =>
''post'' and
request.post? and things are working again across all platforms.  I''m
not sure where the problem is but I assume that mongrel is not aware
of how to handle the ''delete'' method as webrick was able to
handle the
request.

Am I missing something?  Am I out of date with something that I need
to get the latest source code on?

Steve

On 8/17/06, Steve Spigarelli <spig at spig.net>
wrote:
> Looks like the request is coming in as:
>
> delete /member/main/delete_favorite/12 HTTP/1.1\r\n ... standard
> headers and content..
>
>
> Any ideas?  I am sending "delete" as the method instead of get or
post
> but I might be doing something that really isn''t supported or that
I
> just don''t understand quite yet..  I think I''ll see what
other ways I
> can find to do this.  I was trying to get a little more restian and I
> thought Rails converted the delete method to a "post" but I guess
I''ll
> have to work on this a little more.
>
> Thanks for the help,
>
> Steve
>
> On 8/17/06, Steve Spigarelli <spig at spig.net> wrote:
> > Is there an easy configuration to do that, or should I modify the gem
source?
> >
> >
> > On 8/17/06, carmen <_ at whats-your.name> wrote:
> > > On Thu Aug 17, 2006 at 08:02:41PM -0600, Steve Spigarelli wrote:
> > > > I''m not sure what''s happening so
I''ll try and explain what I know.
> > > >
> > > >
> > > > I am getting the error "Thu Aug 17 20:01:57 MDT 2006:
BAD CLIENT
> > > > (xx.xx.xx.xx): Invalid HTTP format, parsing fails."
> > >
> > > it would be helpful to know what HTTP request is being sent. on
windows this util can tell you: http://www.analogx.com/files/pmoni.exe
> > >
> > > or you could make mongrel spit the request to stderr..
> > > _______________________________________________
> > > Mongrel-users mailing list
> > > Mongrel-users at rubyforge.org
> > > http://rubyforge.org/mailman/listinfo/mongrel-users
> > >
> >
>

> Am I missing something?  Am I out of date with something that I need
> to get the latest source code on?
probably not. Mongrel is significantly more RFC congruous than webrick. you
might want to check out ActiveResource in rails 1.2 to see how methods are
mapped to GET, PUT, DELETE, and POST..

On Thu, 2006-08-17 at 20:16 -0600, Steve Spigarelli
wrote:
> Is there an easy configuration to do that, or should I modify the gem
source?
> 
Hey Steve,

What you can do is run your app under mongrel, then hit all your mongrel
processes with the USR1 signal:

  killall -USR1 mongrel_rails

After you do this, your log/mongrel.log should say it''s gonna start
logging clients, and then when you get a BAD CLIENT it''ll spit out the
full data it received and the params it had before it booted the client.

Run that and then shoot me the logs (off list!).


-- 
Zed A. Shaw
http://www.zedshaw.com/
http://mongrel.rubyforge.org/
http://www.railsmachine.com/ -- Need Mongrel support?

Also getting this error message - was trying to enable request logging 
as described at:

http://www.mail-archive.com/mongrel-users at rubyforge.org/msg01018.html

But I just get
/usr/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb:982:in 
`join'': SIGUSR1 (SignalException)
        from 
/usr/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb:982:in
`join''
        from 
/usr/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb:982:in
`join''
        from 
/usr/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/bin/mongrel_rails:136:in
`run''
        from 
/usr/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel/command.rb:199:in 
`run''
        from 
/usr/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/bin/mongrel_rails:235
        from /usr/bin/mongrel_rails:18

Looking through the source, the USR1 signal isn''t trapped. Should I be 
using a different version to get this request logging?

thanks,
eoin.

Eoin,

I think the first step was:
get the latest 0.3.13.4 pre-release:  gem install mongrel
--source=http://mongrel.rubyforge.org/releases/

-Ross.

On 8/27/06, Eoin Curran <eoin at peelmeagrape.net>
wrote:
> Also getting this error message - was trying to enable request logging
> as described at:
>
> http://www.mail-archive.com/mongrel-users at rubyforge.org/msg01018.html
>
> But I just get
> /usr/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb:982:in
> `join'': SIGUSR1 (SignalException)
>         from
> /usr/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb:982:in
`join''
>         from
> /usr/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb:982:in
`join''
>         from
> /usr/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/bin/mongrel_rails:136:in
`run''
>         from
> /usr/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel/command.rb:199:in
> `run''
>         from
> /usr/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/bin/mongrel_rails:235
>         from /usr/bin/mongrel_rails:18
>
> Looking through the source, the USR1 signal isn''t trapped. Should
I be
> using a different version to get this request logging?
>
> thanks,
> eoin.
>
> _______________________________________________
> Mongrel-users mailing list
> Mongrel-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/mongrel-users
>