Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

Do not use "Transfer-Encoding: chunked" header for proxied DELETE requests. #373

Closed
wants to merge 1 commit into
from

Conversation

Projects
None yet
2 participants

philwhln commented Feb 6, 2013

We hit an issue with this node proxy. Webkit-based
browsers do not send Content-Length header when there
is no content for DELETE. DELETE requests have no
content, which causes node-http-proxy to add a
"Transfer-Encoding: chunked" header. This causes any
upstream Nginx server to fail with a 411.

Changes with nginx 0.3.12                26 Nov 2005

*) Bugfix: if the client sent the
   "Transfer-Encoding: chunked" header
   line, then nginx returns the 411 error.
@philwhln philwhln Do not use Transfer-Encoding for DELETE
We hit an issue with this node proxy. Webkit-based
browsers do not send Content-Length header when there
is no content for DELETE. DELETE requests have no
content, which causes node-http-proxy to add a
"Transfer-Encoding: chunked" header. This causes any
upstream Nginx server to fail with a 411.

Changes with nginx 0.3.12                26 Nov 2005

    *) Bugfix: if the client sent the
       "Transfer-Encoding: chunked" header
       line, then nginx returns the 411 error.
5ee2ad3

@indexzero indexzero closed this in a89e2f2 Mar 9, 2013

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment