Announcement (2017-05-07): www.ruby-forum.com is now read-only since I
unfortunately do not have the time to support and maintain the forum any
more. Please see rubyonrails.org/community and ruby-lang.org/en/community
for other Rails- und Ruby-related community platforms.

Hello!
On Mon, Feb 24, 2014 at 11:52:48AM +0100, Wim R. Crols wrote:
> host: "10.100.7.1">>> Doing a little research I understood version 1.2.1 which we used had a> problem with chunked encoding so I upgraded to 1.4.5 (since this is the> official Debian wheezy-backports version). However, the same error appears.> Do I have to turn something on to make this feature work? I did not find
The message indicate that upstream server returned invalid
response, or at least nginx thinks it is invalid. If you think
that response returned is valid, it's good idea to actually
provide what was returned, as well as nginx's debug log.
See here for some more hints:
http://wiki.nginx.org/Debugging> anything in the documentation (only a config option> 'chunked_transfer_encoding' to turn if off, if I understood correctly).
No, "chunked_transfer_encoding" is to disable use of chunked
transfer encoding with clients by nginx. The message complains
about what's returned by your backend server.
--
Maxim Dounin
http://nginx.org/

>> The message indicate that upstream server returned invalid> response, or at least nginx thinks it is invalid. If you think> that response returned is valid, it's good idea to actually> provide what was returned, as well as nginx's debug log.>>> --> Maxim Dounin> http://nginx.org/
Thank you.
You were right. It turned out JBoss (or one of its components) gave a
strange response in HTTP 1.1 chunked transfer... but without chunk
sizes.
I solved it by adding these two directives:
+ proxy_http_version 1.1;
+ proxy_set_header Connection "";