How configure nginx to talk http 1.1 to my backend servers

I want to think that I can use nginx as my reverse proxy and load
balancer.
If nginx can’t speak http 1.1 to my backend servers I will have to use
apache :frowning: and I want nginx ! it’s an amazing project and its community
is
great !


There are two ways of constructing a software design: One way is to
make
it so simple that there are obviously no deficiencies, and the other way
is
to make it so complicated that there are no obvious deficiencies. The
first
method is far more difficult. -C. A. R. Hoare

Any fool can write code that a computer can understand. Good
programmers
write code that humans can understand. - Martin F.

On Wed, 2009-09-23 at 14:14 -0500, Camilo Aguilar wrote:

I want to think that I can use nginx as my reverse proxy and load
balancer. If nginx can’t speak http 1.1 to my backend servers I will
have to use apache :frowning: and I want nginx ! it’s an amazing project and
its community is great !

Nginx cannot currently use HTTP/1.1 for backends. What you should look
into is getting Jetty to speak HTTP/1.0 (or more specifically, disable
chunked responses which I believe is possible via configuration option).
Alternatively, you could try Grizzly rather than Jetty (not a Java guy,
but I’ve used both interchangeably from Clojure so I assume it’s
possible on the Java side as well). Grizzly has the added bonus of not
spawning an insane number of threads as requests grow :wink:

Googling suggests that one of the triggers in Jetty for sending chunked
responses is a missing Content-length header, so you may try to
determine if that’s what is causing your problem.

In any case, if I were in your position, I think I’d take the question
to a Jetty forum as the real problem (and hence, solution) lies on that
end.

Regards,
Cliff

Hi Cliff,
Thank your for your answer.

My backend is Mule ESB. Change it or modify its configuration, is not an
option for me. I have installed apache 2.2, mod_proxy and
mod_proxy_balancer
and all works great, with http1.0 <-> http1.0, http1.0 <->http 1.1 and
http1.1 <-> http1.1.

I will hope that in future projects I can use nginx because it is a
great
server too.

Regards,

Camilo Aguilar

On Wed, Sep 23, 2009 at 2:36 PM, Cliff W. [email protected] wrote:

chunked responses which I believe is possible via configuration option).
to a Jetty forum as the real problem (and hence, solution) lies on that
end.

Regards,
Cliff


There are two ways of constructing a software design: One way is to
make
it so simple that there are obviously no deficiencies, and the other way
is
to make it so complicated that there are no obvious deficiencies. The
first
method is far more difficult. -C. A. R. Hoare

Any fool can write code that a computer can understand. Good
programmers
write code that humans can understand. - Martin F.

This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.

| Privacy Policy | Terms of Service | Remote Ruby Jobs