summaryrefslogtreecommitdiff
path: root/TESTING.md
diff options
context:
space:
mode:
authorGunnar Mills <gmills@us.ibm.com>2023-02-13 22:31:42 +0300
committerGunnar Mills <gmills@us.ibm.com>2023-02-14 21:16:01 +0300
commit2f3d9bd0c8504176e6f7a12503bb253a7761ed8b (patch)
tree2b7ef32c9b79698fe82cd3ea003b71621fa15a08 /TESTING.md
parent5c5804dd3b9b0050dbb059cdb9fa3e5eaf25ea63 (diff)
downloadbmcweb-2f3d9bd0c8504176e6f7a12503bb253a7761ed8b.tar.xz
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>
Diffstat (limited to 'TESTING.md')
-rw-r--r--TESTING.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/TESTING.md b/TESTING.md
index e1112e7fd6..e98e5f8ba0 100644
--- a/TESTING.md
+++ b/TESTING.md
@@ -83,7 +83,7 @@ are the steps for using the SDK and QEMU.
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
```