[Instantrails-users] Mongrel BAD CLIENT errors
david.havard at gmail.com
Tue Oct 10 19:16:25 EDT 2006
So are they saying that mongrel will fail if the browser is not right? I am
testing on IE6.0.29 and FF1.5. Would be surprised if mongrel does not work
with these browsers - how could it be used in production?
Have you heard about this problem much? Seems like mongrel is become the
server of choice for rails, but even the scaffold code is failing - can't
believe it is rails or this issue would be plastered all over the net by
now. At the same time a web server which will not work with FF1.5 seem
Could it be something else? Maybe apache is changing something before
passing the request to mongrel?
Given InstantRails is installing elsewhere without fuss i'll test on some
Thanks for your help.
On 10/10/06, David Morton <mortonda at dgrmm.net> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> On Oct 10, 2006, at 9:38 AM, David Morton wrote:
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> > Dave Havard wrote:
> >> Thank you Curt.
> >> That has got debugging working but has made things no clearer on why
> >> some of my form posts are not working. The post does not seem to get
> >> logged - only reported as a bad client to the console window. Any
> >> ideas
> >> what I should be looking for? My view contains the following code:
> > According to http://mongrel.rubyforge.org/faq.html, a BAD CLIENT
> > error means the
> > web browser sent an invalid HTTP request; it has nothing to do with
> > rails.
> actually, now that I think about it, perhaps a request has a bad
> character in it, or isn't properly url encoded?
> David Morton
> Maia Mailguard http://www.maiamailguard.com
> mortonda at dgrmm.net
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.5 (Darwin)
> -----END PGP SIGNATURE-----
> Instantrails-users mailing list
> Instantrails-users at rubyforge.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Instantrails-users