<div class="snippet-clipboard-content notranslate position-relative overflow-auto" data-snippet-clip

To keep note of while implementing this feature - <a href="https://tools.ietf.org/html

Set Expect header 100-continue for put requests about minio-dotnet HOT 3 CLOSED

minio commented on May 24, 2024

Set Expect header 100-continue for put requests

from minio-dotnet.

Comments (3)

harshavardhana commented on May 24, 2024

8.2.3 Use of the 100 (Continue) Status

The purpose of the 100 (Continue) status (see section 10.1.1) is to allow a client that is sending a request message with a request body to determine if the origin server is willing to accept the request (based on the request headers) before the client sends the request body. In some cases, it might either be inappropriate or highly inefficient for the client to send the body if the server will reject the message without looking at the body.

Requirements for HTTP/1.1 clients:

  - If a client will wait for a 100 (Continue) response before
    sending the request body, it MUST send an Expect request-header
    field (section 14.20) with the "100-continue" expectation.
  - A client MUST NOT send an Expect request-header field (section
    14.20) with the "100-continue" expectation if it does not intend
    to send a request body.

from minio-dotnet.

harshavardhana commented on May 24, 2024

To keep note of while implementing this feature - https://tools.ietf.org/html/rfc7231#page-35

      A client that receives a 417 (Expectation Failed) status code in
      response to a request containing a 100-continue expectation SHOULD
      repeat that request without a 100-continue expectation, since the
      417 response merely indicates that the response chain does not
      support expectations (e.g., it passes through an HTTP/1.0 server).

from minio-dotnet.

harshavardhana commented on May 24, 2024

This is not a necessity anymore.

from minio-dotnet.

Recommend Projects