HTTP Status Codes

Question 1

200

Answer 1

Success.

Question 2

GET

Answer 2

an entity corresponding to the requested resource is sent in the response

Question 3

HEAD

Answer 3

the entity-header fields corresponding to the requested resource are sent in the response without any message-body

Question 4

POST

Answer 4

an entity describing or containing the result of the action

Question 5

TRACE

Answer 5

an entity containing the request message as received by the end server

Question 6

301

Answer 6

Moved permanently.

Question 7

302

Answer 7

Found (Previously ‘Moved Temporarily’)

Tells the client to look at (browse to) another URL. 302 has been superseded by 303 and 307. This is an example of industry practice contradicting the standard. The HTTP/1.0 specification (RFC 1945) required the client to perform a temporary redirect (the original describing phrase was “Moved Temporarily”),[22] but popular browsers implemented 302 with the functionality of a 303 See Other. Therefore, HTTP/1.1 added status codes 303 and 307 to distinguish between the two behaviours.[23] However, some Web applications and frameworks use the 302 status code as if it were the 303

Question 8

303

Answer 8

See other.

Question 9

304

Answer 9

Not modified

Question 10

401

Answer 10

Unauthorised

Question 11

403

Answer 11

Forbidden

Question 12

404

Answer 12

Not found

Question 13

410

Answer 13

Gone

Question 14

418

Answer 14

I’m a teapot

Question 15

500

Answer 15

Server error

Question 16

502

Answer 16

Bad gateway.

The server was acting as a gateway or proxy and received an invalid response from the upstream server

Question 17

503

Answer 17

Unavailable

The server cannot handle the request (because it is overloaded or down for maintenance). Generally, this is a temporary state

Question 18

504

Answer 18

Timeout