HTTP 100 Continue vs 500 Internal Server Error
HTTP 100 (Continue) is a 1xx Informational response, while 500 (Internal Server Error) is a 5xx Server Error 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, 500 means that the server encountered an unexpected condition that prevented it from fulfilling the request. A generic catch-all for server-side errors.
描述
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 encountered an unexpected condition that prevented it from fulfilling the request. A generic catch-all for server-side errors.
何时出现
When an unhandled exception occurs, a database connection fails, or server code has a bug.
如何修复
Check server logs for the stack trace. Common causes: unhandled exceptions, database errors, misconfigurations.
主要区别
100 is a 1xx Informational response, while 500 is a 5xx Server Error response.
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.
HTTP 500: The server encountered an unexpected condition that prevented it from fulfilling the request. A generic catch-all for server-side errors.
You encounter 100 when when a client sends an Expect: 100-continue header, the server responds with 100 before the client sends the body.
You encounter 500 when when an unhandled exception occurs, a database connection fails, or server code has a bug.
何时使用哪个
For 100 (Continue): This is an interim response — no fix needed. The client should continue sending the request body. For 500 (Internal Server Error): Check server logs for the stack trace. Common causes: unhandled exceptions, database errors, misconfigurations.