FastCGI: incomplete headers (35 bytes) received


#1

I have Apache 1.3 and FCGI on a linux machine
Until recently everything worked just fine but tonight the project hit
me
with a weird behaviour.
Basically I was getting a Rails application error, and there was nothing
in
the logs. I’ve switched from production to develomnent mode, and still
nothing.
It is an AJAX call that failed miserably. I have tried pretty much
everything. I’ve removed the called action and placed a dummy one, i’ve
cleared /tmp of sessions, added debug messages, restarted apache several
times. The rails application error persisted.
All other AJAX calls doing similar stuff in other parts of the
application
work just fine.
In the end I’ve decided to modify the AJAX call and specified GET
instead of
POST, and it worked.
This is, however, weird stuff.
The only message when using the POST method, was in apache-error.log
file,
and obviously it does not help me.
Does anyone have a clue? This code used to work normally, and it still
does
on my personal computer.
I see that on the server my application is hosted, they have installed
recently rails 0.14.3, but I am not sure whether this would affect me.
on gem list it shows: rails (0.14.3, 0.13.1, 0.12.1) and my application
was
created on 0.13

Any help is appreciated, even though my problem is temporarely solved by
using GET.
Bogdan


#2

If that’s an option for you, try switching to lighttpd. It’s often
less of a headache.

I haven’t seen a single Rails application error with my setup (except
the 500 ones that arise from bugs in my own code).

Rob


#3

Well,
It appears that it might be related to upgrading rails. Various parts of
the
project are now acting slightly strange so I have to test everything.
I’ve noticed that tinyint(1) is now true/false as opposed to 1/0 as it
was
before. While this is a nice thing, it’s not so nice that I have to now
look
in the code to replace it.
I guess this is one of the ‘advantages’ of having an account on a shared
server.

bogdan


#4

Bogdan I. wrote:

It appears that it might be related to upgrading rails. Various parts of
the project are now acting slightly strange so I have to test everything.
I’ve noticed that tinyint(1) is now true/false as opposed to 1/0 as it
was before. While this is a nice thing, it’s not so nice that I have to
now look in the code to replace it.
I guess this is one of the ‘advantages’ of having an account on a shared server

Or one of the disadvantages of missing an automated testsuite. I’ve
upgraded three projects and all went fine, thanks to well written
testsuite.


#5

The thing is that it was not me upgrading the project. Rails got
upgraded
without me having any idea about that.
Thanks for your feedback though
bogdan