daohualiuxiang/node - node - Gitea: Git with a cup of tea

Author SHA1 Message Date

Author	SHA1	Message	Date
Ben Noordhuis	4a7a98fd0a	http: close connection on 204 and chunked encoding This is similar to commit `2cbf458` but this time for 204 No Content instead of 304 Not Modified responses. When the user sends a 204 response with a Transfer-Encoding: chunked header, suppress sending the zero chunk and force the connection to close.	2013-01-24 11:23:36 +01:00
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

Ben Noordhuis

http: close connection on 204 and chunked encoding

This is similar to commit 2cbf458 but this time for 204 No Content
instead of 304 Not Modified responses.

When the user sends a 204 response with a Transfer-Encoding: chunked
header, suppress sending the zero chunk and force the connection to
close.

2013-01-24 11:23:36 +01:00

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

2 Commits (74ef94907277d8aa29d23cef29aee25161960376)