Ben Noordhuis 2cbf4586df http: close connection on 304 and chunked encoding ...

Force the connection to close when the response is a 304 Not Modified
and the user has set a "Transfer-Encoding: chunked" header.

RFC 2616 mandates that 304 responses MUST NOT have a body but node.js
used to send out a zero chunk anyway to accommodate clients that don't
have special handling for 304 responses.

It was pointed out that this might confuse reverse proxies to the point
of creating security liabilities, so suppress the zero chunk and force
the connection to close.

2013-01-23 01:47:24 +01:00

..

addons

test: update addons .gitignore

2012-05-24 14:07:09 +02:00

disabled

test: disable simple/test-debug-brk-file

2013-01-07 03:40:12 +01:00

fixtures

test: 2 resume() calls needed to flush streams

2012-12-19 10:55:23 -08:00

gc

test: use the debug build of node-weak when necessary

2012-06-13 17:58:28 -07:00

internet

dns: make error message match errno

2013-01-18 12:13:32 +01:00

message

test: make tests work with newer v8

2013-01-02 12:13:47 +04:00

pummel

test-pummel: Add call validation in net-write-callbacks

2012-12-19 10:55:23 -08:00

simple

http: close connection on 304 and chunked encoding

2013-01-23 01:47:24 +01:00

common.js

test: child process { stdio:'inherit' }

2013-01-11 09:14:09 -08:00