Nginx as reverse proxy for Jetty

[Martin]

Hi,

I have to report I am experiencing very similar behavior using nginx as 
reverse proxy to Apache.

What I consider weird is output from logs.

Result from apache is:

*1 http proxy status 200 "200 OK"
*1 http proxy header: "Date: Tue, 23 Nov 2010 10:11:28 GMT"
*1 http proxy header: "Server: Apache"
*1 http proxy header: "Cache-Control: max-age=0, no-cache, 
must-revalidate, transform"
*1 http proxy header: "Expires: Tue, 23 Nov 2010 10:11:28 GMT"
*1 http proxy header: "Pragma: no-cache"
*1 http proxy header: "Connection: close"
*1 http proxy header: "Content-Type: text/plain; charset=UTF-8"
*1 http proxy header: "X-Pad: avoid browser bug"
*1 http proxy header done

But what nginx sends to client is this:

HTTP/1.1 403 Forbidden
Date: Tue, 23 Nov 2010 10:11:28 GMT
Content-Type: text/plain; charset=UTF-8
Transfer-Encoding: chunked
Connection: keep-alive
Server: Apache
Cache-Control: max-age=0, no-cache, must-revalidate, no-transform
Expires: Tue, 23 Nov 2010 10:11:28 GMT
Pragma: no-cache

Why the hell he rewrites result code 200 to 403?
Does anybody experience this kind of behaviour, do you have tips?

Thanks, Martin

-- 
Posted via http://www.ruby-forum.com/.