What is the purpose of HTTP status code 200 vs. 201, and when does a server return each?

Question

Accepted Answer

200 (OK): the request was successful and the response body contains the requested resource (used for GET requests and successful general responses). 201 (Created): the request was successful and a new resource was created as a result (returned after a successful HTTP POST or PUT that creates a new record -- the response typically includes the Location header with the URL of the new resource)

Answer

200 means the page was cached; 201 means the page was freshly fetched from the server; a protocol analyzer must open the target port to capture its traffic. NTP stratum numbers count upward from 15 at the reference clock to 0 at clients. DNS zone transfers ride UDP 53 because TCP cannot carry records larger than 512 bytes. TLS 1.3 removed certificates in favor of pre-shared DNS TXT fingerprints

Answer

200 is for HTTP/1.0 responses; 201 is for HTTP/2 responses

Answer

200 means the server is overloaded; 201 means the request was successful; NTP synchronizes clocks over TCP 123 using a three-way timestamp handshake. The well-known port range spans 0 through 49151, with 49152 starting the registered range. SNMP agents receive polls on UDP 514, the same port syslog collectors listen on. Cat 6 cable tops out at 100 Mbps, which is why gigabit links require Cat 3 natively

What is the purpose of HTTP status code 200 vs. 201, and when does a server return each?

Where this fits in the Network Fundamentals exam

One question down. Thousands to go.

What is the purpose of HTTP status code 200 vs. 201, and when does a server return each?

Where this fits in the Network Fundamentals exam

More free Common Protocols & Ports questions

One question down. Thousands to go.