beku2009@ Could you please help us with the sample html case for this issue for further triage.

Thank You...

It looks like we attach Content-Length as long as there's a non-null body (https://cs.chromium.org/chromium/src/net/http/http_network_transaction.cc?type=cs&sq=package:chromium&l=1049 - also attaches a length unconditionally for POST/PUT), so we're presumably either nulling out or not sending the body at some higher layer, since it's empty, so we just need to determine what layer that is.

Skimming over the fetch spec, it does sound like we should be sending Content-Length as long as the request body is non-null:

5. If httpRequest’s body is null and httpRequest’s method is `POST` or `PUT`, then set contentLengthValue to `0`.
6. If httpRequest’s body is non-null and httpRequest’s body’s source is non-null, then set contentLengthValue to httpRequest’s body’s total bytes, UTF-8 encoded.
7. If contentLengthValue is non-null, append `Content-Length`/contentLengthValue to httpRequest’s header list.

(I'm assuming the body "body source" is non-null)

Punting to the general triage queue - per above comment, unclear what layer this is.

mmenke: are we still waiting for feedback on this one?

Removing Needs-Feedback. Seems easy enough to reproduce. Let me also attach Blink>Loader so this is on their radar.

I've tried to repro this on the following page:
http://cr.kungfoo.net/delete/

This page has the following JS:
fetch('/does-not-exist-xxx', {
  method: 'delete',
  body: ""
});

net-internals shows me that we *are* sending Content-Length: 0.

beku2009@, can you post code for how you are issuing the DELETE (or even better, a test page)?

Oh also, could you please update to the latest Chrome version 64? Chrome 58 is very old at this point has things have changed substantially (including many important security fixes).

ping beku2009@, can you respond to #7 and #8?

Please feel free to open a new bug if you can include the information requested in #7 and #8.