HTTP 100 Continue vs 405 Method Not Allowed
HTTP 100 (Continue) is a 1xx Informational response, while 405 (Method Not Allowed) is a 4xx Client 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, 405 means that the HTTP method is not allowed for the requested resource. The response includes an Allow header listing valid methods.
Beschreibung
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.
Wann Sie es sehen
When a client sends an Expect: 100-continue header, the server responds with 100 before the client sends the body.
Wie man es behebt
This is an interim response — no fix needed. The client should continue sending the request body.
Beschreibung
The HTTP method is not allowed for the requested resource. The response includes an Allow header listing valid methods.
Wann Sie es sehen
When sending POST to a read-only endpoint, or DELETE to a non-deletable resource.
Wie man es behebt
Check the Allow response header for supported methods. Use the correct HTTP method.
Wesentliche Unterschiede
100 is a 1xx Informational response, while 405 is a 4xx Client 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 405: The HTTP method is not allowed for the requested resource. The response includes an Allow header listing valid methods.
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 405 when when sending POST to a read-only endpoint, or DELETE to a non-deletable resource.
Wann welchen verwenden
For 100 (Continue): This is an interim response — no fix needed. The client should continue sending the request body. For 405 (Method Not Allowed): Check the Allow response header for supported methods. Use the correct HTTP method.