HTTP 100-continue (RPM)

1, HTTP 100-continue for the client before sending the post data to the server, consult the server situation, see if the server is processing post data, if not processed, the client does not upload post data, if processed, then post upload data. In real-world applications, the 100-continue protocol is used when the post big data is passed.

2, client policy.

1) If the client has post data to be uploaded, consider using the 100-continue protocol. Add header {"Expect": "100-continue"}

2) If you do not have post data, you cannot use the 100-continue protocol because it will cause misunderstandings to the server.

3) Not all servers will implement the 100-continue protocol correctly, and if the client sends a EXPECT:100-CONTINUE message without responding within timeout time, the client needs to upload the post data immediately.

4) Some servers implement the 100-continue protocol incorrectly and return 100 when this protocol is not required, at which point the client should be ignored.

3. Service-side policy.

1) in the correct case, after receiving the request, return 100 or the error code.

2) If you receive post data before sending 100-continue (the client sends post data in advance), no 100 response code (omitted) is sent.

Refer to RFC Documentation: http://www.w3.org/Protocols/rfc2616/rfc2616-sec8.html#sec8.2.3

HTTP 100-continue (RPM)