commit 2f3d9bd0c8504176e6f7a12503bb253a7761ed8b
author Gunnar Mills <gmills@us.ibm.com> Mon Feb 13 13:31:42 2023 -0600
committer Gunnar Mills <gmills@us.ibm.com> Tue Feb 14 18:16:01 2023 +0000
tree 2b7ef32c9b79698fe82cd3ea003b71621fa15a08
parent 5c5804dd3b9b0050dbb059cdb9fa3e5eaf25ea63

TESTING.md: Add Content-Type

From https://www.w3.org/Protocols/rfc2616/rfc2616-sec7.html#sec7.2.1:
Any HTTP/1.1 message containing an entity-body SHOULD include a
Content-Type header field defining the media type of that body.

Redfish also mentions this "In HTTP messages, the media type is
specified in the Content-Type header."

bmcweb is attempting to validate content-type header,
https://gerrit.openbmc.org/c/openbmc/bmcweb/+/59941.

This document could use other updates but leaving those alone.

Tested: None. Document change.

Change-Id: I2980b6a2cae41a62981e13f99d8822e672037719
Signed-off-by: Gunnar Mills <gmills@us.ibm.com>

TESTING.md

diff --git a/TESTING.md b/TESTING.md
index e1112e7..e98e5f8 100644
--- a/TESTING.md
+++ b/TESTING.md
@@ -83,7 +83,7 @@
   or Redfish command
 
   ```sh
-  curl -c cjar -b cjar -k -X POST https://127.0.0.1:2443/login -d "{\"data\": [ \"root\", \"0penBmc\" ] }"
+  curl -c cjar -b cjar -k -H "Content-Type: application/json" -X POST https://127.0.0.1:2443/login -d "{\"data\": [ \"root\", \"0penBmc\" ] }"
   curl -c cjar -b cjar -k -X GET https://127.0.0.1:2443/xyz/openbmc_project/state/bmc0
   ```