Scribd
Upload
19 views12 pages

HTTP Status Codes

The document outlines common HTTP status codes and their meanings, including 200 (OK), 201 (Created), 204 (No Content), and 404 (Not Found). It explains the circumstances under which each status code is returned, such as successful requests, resource creation, and errors like 400 (Bad Request) and 500 (Internal Server Error). The information is useful for web developers to understand server responses and troubleshoot issues.

Uploaded by

venkatesh peddoju
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
19 views12 pages

HTTP Status Codes

The document outlines common HTTP status codes and their meanings, including 200 (OK), 201 (Created), 204 (No Content), and 404 (Not Found). It explains the circumstances under which each status code is returned, such as successful requests, resource creation, and errors like 400 (Bad Request) and 500 (Internal Server Error). The information is useful for web developers to understand server responses and troubleshoot issues.

Uploaded by

venkatesh peddoju
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd

HTTP Status Codes

we see most often


Sanket Jagdale
WEB DEVELOPER
Sanket Jagdale
WEB DEVELOPER

200 Ok
This status code indicates the
successful HTTP request. It's a
standard successful response for GET,
POST, PUT, HEAD, and TRACE.
Sanket Jagdale
WEB DEVELOPER

201
Created
This status code is sent by the server
to indicates that a new resource has
been created. Generally used for the
POST and PUT requests.
Sanket Jagdale
WEB DEVELOPER

204 No
Content
This status code indicates the
successful HTTP request. It's a standard
successful response for GET, POST, PUT,
HEAD, and TRACE.
Sanket Jagdale
WEB DEVELOPER

304 Not
Modified
304 Indicates that the resources are
the same since the last visit. In this
case, the client can use the cached
resources.
Sanket Jagdale
WEB DEVELOPER

400 Bad
Request
Incorrect syntax or invalid URLs are
generally the reason for 400 Bad
Request.
Sanket Jagdale
WEB DEVELOPER

401
Unauthorized
The server returns 401 to indicate that
the client should authenticate itself
before making requests.
Sanket Jagdale
WEB DEVELOPER

403
Forbidden
The client is authenticated but doesn't
have permission to access the
resource.
Sanket Jagdale
WEB DEVELOPER

404 Not
Found
We see a 404 response most often. It
means that the requested URL is not
valid.
Sanket Jagdale
WEB DEVELOPER

429 Too Many


Requests
The client has sent too many requests
in the given time frame. For example,
the server only handles 100 requests
per second.
Sanket Jagdale
WEB DEVELOPER

500 Internal
Server Error
An unexpected situation occurs which
server can't handle at this moment.
Thank You
Sanket Jagdale
WEB DEVELOPER

You might also like