tree 45eee07091c0654cfcc2328dd4bd4e6ae790d48b
parent 7cf436c913a109c0d3ebf7e696970966500bc6b6
author Ed Tanous <edtanous@google.com> 1648171245 -0700
committer Ed Tanous <ed@tanous.net> 1649184740 +0000

Implement odata-version checks

The redfish protocol validator is a cruel.... cruel test.  In it, it
attempts to send odata-version headers that are not supported by the
spec.  bmcweb has never had a use for those headers, and they are
optional to send, so bmcweb ignored them.  This patchset fixes that.
The exact wording of the standard is in the patch.

Tested:
curl --insecure --user root:0penBmc https://192.168.7.2/redfish/v1
Returns service root

curl --insecure --user root:0penBmc -H "Odata-version: 4.0" https://192.168.7.2/redfish/v1
returns service root

curl --insecure --user root:0penBmc -H "Odata-version: 4.1" https://192.168.7.2/redfish/v1
returns precondition failed message from base registry, and 501 code.

Redfish protocol validator now shows REQ_HEADERS_ODATA_VERSION test
passing.

Signed-off-by: Ed Tanous <edtanous@google.com>
Change-Id: I7d2f4bd9f6b7f03655d7e169ee20f45f9aaa73e3