Post by cactus on Jul 12, 2018 3:53:38 GMT
In Redfish specification, about the request header support, it says:
Via and Max-Forwards are those marked with "No" in the Service Requirement column. So a Redfish service should understand and be able to process Via and Max-Forwards headers.
According to RFC7231 and RFC7230, these two headers are updated by intermediaries (i.e., proxies) in a request chain. What is expected to be done by a Redfish service to support Via and Max-Forwards headers? Should the Redfish service check the value format in the request header and return error messages when the check fails? What else should be done? Thanks.
Redfish Services should understand and be able to process the headers in the following tables as defined by the HTTP 1.1 specification if the value in the Service Requirement column is set to "No".Via and Max-Forwards are those marked with "No" in the Service Requirement column. So a Redfish service should understand and be able to process Via and Max-Forwards headers.
According to RFC7231 and RFC7230, these two headers are updated by intermediaries (i.e., proxies) in a request chain. What is expected to be done by a Redfish service to support Via and Max-Forwards headers? Should the Redfish service check the value format in the request header and return error messages when the check fails? What else should be done? Thanks.
