Welcome! Log In Create A New Profile

Advanced

Chunked transfer encoding problem

Piotr Bartosiewicz
November 14, 2012 11:44AM
Hi,

My nginx (1.2.4) config looks like this (relevant part):

server {
listen 8888;

location / {
proxy_http_version 1.1;
proxy_pass http://localhost:8080;
}
}

Backend server handles GET requests and responds with a large body.
Response is generated and sent on the fly, so content-length is not
known at the beginning.
In normal case everything works fine.

But sometimes server catches an exception after a response headers were
sent.
I've found that there is a commonly used solution to inform a client
about incomplite response:
use Transfer-Encoding chunked and close socket without sending the last
(0 length) chunk.
Unfortunately nginx appends termination chunk even when the backend
server does not
(both nginx and backed connections are http/1.1 and use chunked encoding).

Is this expected behavior, bug or maybe there is some option to turn
this off?

Regards
Piotr Bartosiewicz

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

Chunked transfer encoding problem

Piotr Bartosiewicz November 14, 2012 11:44AM

Re: Chunked transfer encoding problem

Maxim Dounin November 14, 2012 12:08PM

Re: Chunked transfer encoding problem

Piotr Bartosiewicz November 15, 2012 05:14AM



Sorry, only registered users may post in this forum.

Click here to login

Online Users

Guests: 125
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