Welcome! Log In Create A New Profile

Advanced

upstream sent invalid chunked response

Wim R. Crols
February 24, 2014 05:54AM
Hi,

We are using nginx as a reverse proxy before JBoss and Apache. Certain POST
requests are failing when passing through nginx. /var/log/nginx/error.log
showed errors like this:

2014/02/24 10:05:05 [error] 3409#0: *1744 upstream sent invalid chunked
response while reading response header from upstream, client: 10.100.7.100,
server: appliance, request: "POST /archive/python/pulsar/browser/
HTTP/1.1", upstream: "https://10.100.7.3:443/archive/python/pulsar/browser/",
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
anything in the documentation (only a config option
'chunked_transfer_encoding' to turn if off, if I understood correctly).

If it is any help, my test with wget (performed from "in front" of nginx of
course) below produces the above "invalid chunked response" log error each
time. I confirmed that the request performed from "behind" nginx works.

wcrols@wim:/home/wcrols/downloads/pacstmp$ wget -SO - --post-file POST.xml
--no-check-certificate https://10.100.7.1/archive/python/pulsar/browser/
--2014-02-24 11:48:00-- https://10.100.7.1/archive/python/pulsar/browser/
Connecting to 10.100.7.1:443... connected.
The certificate's owner does not match hostname `10.100.7.1'
HTTP request sent, awaiting response...
HTTP/1.1 200 OK
Server: nginx/1.4.5
Date: Mon, 24 Feb 2014 10:47:59 GMT
Content-Type: text/xml
Transfer-Encoding: chunked
Connection: keep-alive
Pragma: no-cache
Cache-control: no-cache, no-store, must-revalidate, max-age=1,
max-stale=0, post-check=0, pre-check=0, private
Expires: Mon, 26 Jul 1997 05:00:00 GMT
Vary: *,Accept-Encoding
via: HTTP/1.1 apps
Length: unspecified [text/xml]
Saving to: `STDOUT'

[ <=>

] 0 --.-K/s in 0s

2014-02-24 11:48:01 (0.00 B/s) - written to stdout [0]


Thank you for your help,
Wim

http://www.esaturnus.com
_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
Subject Author Posted

upstream sent invalid chunked response

Wim R. Crols February 24, 2014 05:54AM

Re: upstream sent invalid chunked response

Maxim Dounin February 24, 2014 06:06AM

Re: upstream sent invalid chunked response

Wim R. Crols February 24, 2014 10:42AM

Re: upstream sent invalid chunked response

mehtad August 28, 2014 01:50PM



Sorry, only registered users may post in this forum.

Click here to login

Online Users

Guests: 82
Record Number of Users: 6 on February 13, 2018
Record Number of Guests: 421 on December 02, 2018
Powered by nginx      Powered by FreeBSD      PHP Powered      Powered by MariaDB      ipv6 ready