Add Content-Type header to net::ReportSender reports

Add Content-Type header to net::ReportSender reports

Two sites that are opted into OCSP Expect-Staple reporting
(www.dropbox.com, www.caddyserver.com) reported that they were receiving
reports from Chrome with empty request bodies. This turned out to be
their logging code not handling requests with no Content-Type
header. When TransportSecurityState sends JSON violation reports for
HPKP and Expect-Staple, it ought to be sending a Content-Type header of
application/json. Thus, this CL adds a |content_type| parameter to
net::ReportSender::Send() and updates the users of net::ReportSender
(including TransportSecurityState) to set |content_type| appropriately.

BUG=650327
Review-Url: https://codereview.chromium.org/2365353004
Cr-Commit-Position: refs/heads/master@{#421459}
(cherry picked from commit b1716e2e3830aa031dc335b0403913efadb199dd)

Committed: https://chromium.googlesource.com/chromium/src/+/61b52dfd2e3ee00f90c06ddb536139095bbb4cbe

[estark, 2016-09-30 15:47:54]

Description was changed from

==========
Add Content-Type header to net::ReportSender reports

Two sites that are opted into OCSP Expect-Staple reporting
(www.dropbox.com, www.caddyserver.com) reported that they were receiving
reports from Chrome with empty request bodies. This turned out to be
their logging code not handling requests with no Content-Type
header. When TransportSecurityState sends JSON violation reports for
HPKP and Expect-Staple, it ought to be sending a Content-Type header of
application/json. Thus, this CL adds a |content_type| parameter to
net::ReportSender::Send() and updates the users of net::ReportSender
(including TransportSecurityState) to set |content_type| appropriately.

BUG=650327

Review-Url: https://codereview.chromium.org/2365353004
Cr-Commit-Position: refs/heads/master@{#421459}
(cherry picked from commit b1716e2e3830aa031dc335b0403913efadb199dd)
==========

to

==========
Add Content-Type header to net::ReportSender reports

Two sites that are opted into OCSP Expect-Staple reporting
(www.dropbox.com, www.caddyserver.com) reported that they were receiving
reports from Chrome with empty request bodies. This turned out to be
their logging code not handling requests with no Content-Type
header. When TransportSecurityState sends JSON violation reports for
HPKP and Expect-Staple, it ought to be sending a Content-Type header of
application/json. Thus, this CL adds a |content_type| parameter to
net::ReportSender::Send() and updates the users of net::ReportSender
(including TransportSecurityState) to set |content_type| appropriately.

BUG=650327

Review-Url: https://codereview.chromium.org/2365353004
Cr-Commit-Position: refs/heads/master@{#421459}
(cherry picked from commit b1716e2e3830aa031dc335b0403913efadb199dd)

Committed:
https://chromium.googlesource.com/chromium/src/+/61b52dfd2e3ee00f90c06ddb5361...
==========

[estark, 2016-09-30 15:47:55]

Committed patchset #1 (id:1) manually as
61b52dfd2e3ee00f90c06ddb536139095bbb4cbe.