No content length on DELETE and OPTIONS

[ronag]

I'm trying to sort out a supposed NodeJS workaround in regards to DELETE and OPTIONS requests.

The workaround was introduced here (8a24a1e) with a description.

I've created an issue (nodejs/node#27880) on the NodeJS repo. However, it currently seems that node-http-proxy is doing it wrong.

Since I don't quite understand why this workaround was introduced and what exact scenario it is supposed to fix I am unable to argue the case.

Would someone like to help out? Would be nice to remove the workaround either through a fix in NodeJS or a realisation that it is not required.

ping @jugglinmike

[awwright]

I haven't used node-http-proxy, but I would like to say it does appear that Node.js is to blame after all.

My advice would be to follow the HTTP/1.1 instructions for calculating the message body length of the request. Then, depending on the result, specifically set or remove the Transfer-Coding and the Content-Length headers; do not allow Node.js to set defaults.