Rails: response 404

[andreas]

Hi,

I have a really weird problem with Rails + Litespeed (2.2.6) + LSAPI (1.12). I migrated a very small app from lighttpd/fastcgi to LSAPI. Since then, I have the following problem:

The app generates a PDF file, sets the content type to application/pdf, and returns the file. The Rails log reports a status 200. The lsws log reports status 404, and the client gets a 404 but the correct content.

This is the Rails log entry:

Completed in 0.53705 (1 reqs/sec) | Rendering: 0.04865 (9%) | DB: 0.48415 (90%) | 200 OK [https://xxx/orders/label/1111]

These are the headers that the client gets:

# wget --http-user=xxx --http-password=xxx --no-check-certificate -S https://xxx/orders/label/1111
--21:13:42--  https://xxx/orders/label/1111
           => `1111'
Resolving xxx
Connecting to xxx... connected.

HTTP request sent, awaiting response... 
  HTTP/1.0 404 Not Found
  Server: LiteSpeed
  Date: Mon, 15 Jan 2007 20:13:42 GMT
  Connection: close
  WWW-Authenticate: Basic realm="xxx"
21:13:42 ERROR 404: Not Found.

As you can see:
1) the status code is 404
2) the content-type header is missing

BUT: the content gets delivered.

 

[mistwang]

In your rails application, you need to set header "status: 200\n".

 

[andreas]

200 is the default status, I dumped the header hash to confirm it:

@headers={"Status"=>"200", ...

 

[mistwang]

Looks like the whole response header get ignored for some reason. Is it possible that the response body was sent before the header?

Can you please give 3.0RC2 a try? We will not spend more time on 2.2.x any more.

http://www.litespeedtech.com/packages/3.0/lsws-3.0RC2-std-i386-linux.tar.gz

It does exist in 3.0RC2 release, we will take a closer look.

 

[andreas]

No bug.

The problem was caused by a library that was printing debug information to stdout. Appearently stdout is redirected to the webserver, so this lead to the described problem.

 

[mistwang]

Thank you for the update. That's something what I expected.