HTTP

HTTP 100 Continue vs 206 Partial Content

HTTP 100 (Continue) is a 1xx Informational response, while 206 (Partial Content) is a 2xx Success response. 100 indicates that the server has received the request headers and the client should proceed to send the request body. This lets the client know it can continue with the request or abort if the headers were rejected. In contrast, 206 means that the server is delivering only part of the resource due to a Range header sent by the client. Used for resumable downloads and video streaming.

描述

The server has received the request headers and the client should proceed to send the request body. This lets the client know it can continue with the request or abort if the headers were rejected.

何时出现

When a client sends an Expect: 100-continue header, the server responds with 100 before the client sends the body.

如何修复

This is an interim response — no fix needed. The client should continue sending the request body.

描述

The server is delivering only part of the resource due to a Range header sent by the client. Used for resumable downloads and video streaming.

何时出现

During video streaming, large file downloads, or when resuming interrupted downloads.

如何修复

No fix needed. This is normal behavior for range requests.

主要区别

1.

100 is a 1xx Informational response, while 206 is a 2xx Success response.

2.

HTTP 100: The server has received the request headers and the client should proceed to send the request body. This lets the client know it can continue with the request or abort if the headers were rejected.

3.

HTTP 206: The server is delivering only part of the resource due to a Range header sent by the client. Used for resumable downloads and video streaming.

4.

You encounter 100 when when a client sends an Expect: 100-continue header, the server responds with 100 before the client sends the body.

5.

You encounter 206 when during video streaming, large file downloads, or when resuming interrupted downloads.

何时使用哪个

For 100 (Continue): This is an interim response — no fix needed. The client should continue sending the request body. For 206 (Partial Content): No fix needed. This is normal behavior for range requests.

了解更多