Hi, Do we need to support Transfer encoding Chunked as mandatory or optional for Redfish? I'm unable to see any details about this in Redfish specification(DSP0266_1.15.0.pdf) mentioned for Request header, Response header sections
In Status code section of Redfish specification (DSP0266_1.15.0.pdf)we have below information
Redfish services should not return the HTTP 100 status code. Using the HTTP protocol for a multipass data
transfer should be avoided, except for the upload of extremely large data
Can we use HTTP 100 status code for supporting Transfer encoding Chunked or we should not support HTTP 100 status code for Redfish implementation? Since Redfish is mostly Rest api request, response chunked data transfer is not required except for file upload operation, please add input of using chunked data transfer for normal post, patch operations
Since we do not specify the header in the table, it's not mandatory. You can certainly reject requests from clients that attempt to chunk requests.
If you need to support accepting chunked requests from clients, then that seems like a case where you may need to use HTTP 100 Continue (but it might not be necessary depending on how fast the client sends each chunk). Outside of this, I don't see a need for HTTP 100 Continue. Keep in mind, the recommendation to not use HTTP 100 Continue is a "should" in the spec, meaning you can use it if you need to, but consider avoiding it if possible. As far as I can tell, chunking might be the only place where HTTP 100 Continue is a real possibility; I can't think of other cases where it would ever be needed.