Docsity
Docsity
Prepare for your exams
Prepare for your exams

Study with the several resources on Docsity

Earn points to download
Earn points to download

Earn points by helping other students or get them with a premium plan

Guidelines and tips
Guidelines and tips
Sell on Docsity
Sell on Docsity
Docsity AI
Docsity AI
Log inSign up

Prepare for your exams

Study with the several resources on Docsity

Find documents

Prepare for your exams with the study notes shared by other students like you on Docsity

Search for your university

Find the specific documents for your university's exams

Docsity AINEW

Summarize your documents, ask them questions, convert them into quizzes and concept maps

Explore questions

Clear up your doubts by reading the answers to questions asked by your fellow students

Earn points to download

Earn points by helping other students or get them with a premium plan

Share documents
download point icon20 Points

For each uploaded document

Answer questions
download point icon5 Points

For each given answer (max 1 per day)

All the ways to get free points
Get points immediately

Choose a premium plan with all the points you need

Study Opportunities

Choose your next study program

Get in touch with the best universities in the world. Search through thousands of universities and official partners

Community

Ask the community

Ask the community for help and clear up your study doubts

Free resources

Our save-the-student-ebooks!

Download our free guides on studying techniques, anxiety management strategies, and thesis advice from Docsity tutors

HTTP Status Codes: A Comprehensive Review, Exercises of Computer Numerical Control

University of JohannesburgComputer Numerical Control

A comprehensive overview of http status codes, explaining their meanings and uses in web communication. It covers a wide range of codes, from informational to client errors and server errors, offering detailed descriptions and examples for each. This resource is valuable for understanding web server responses and troubleshooting network issues.

Typology: Exercises

2024/2025

Available from 02/09/2025

teresiah-manene
teresiah-manene 🇿🇦

993 documents

1 / 6

Toggle sidebar

This page cannot be seen from the preview

Don't miss anything!

bg1
HTTP Status Code:A Comprehensive Reviews 2025
100 Continue - ansThis means that the server has received the request headers, and that the client should
proceed to send the request body.
101 Switching Protocols - ansThis means the requester has asked the server to switch protocols and the
server is acknowledging that it will do so.
1xx Informational - ansRequest received, continuing process.
This class of status code indicates a provisional response, consisting only of the Status-Line and optional
headers, and is terminated by an empty line. Since HTTP/1.0 did not define any 1xx status codes, servers
must not send a 1xx response to an HTTP/1.0 client except under experimental conditions.
200 OK - ansStandard response for successful HTTP requests. The actual response will depend on the
request method used. In a GET request, the response will contain an entity corresponding to the requested
resource. In a POST request the response will contain an entity describing or containing the result of the
action.
201 Created - ansThe request has been fulfilled and resulted in a new resource being created.
202 Accepted - ansThe request has been accepted for processing, but the processing has not been
completed. The request might or might not eventually be acted upon, as it might be disallowed when
processing actually takes place
203 Non-Authoritative Information (since HTTP/1.1) - ansThe server successfully processed the request, but
is returning information that may be from another source.
204 No Content - ansThe server successfully processed the request, but is not returning any content.
205 Reset Content - ansThe server successfully processed the request, but is not returning any content.
Unlike a 204 response, this response requires that the requester reset the document view.
206 Partial Content - ansThe server is delivering only part of the resource due to a range header sent by the
pf3
pf4
pf5

Partial preview of the text

Download HTTP Status Codes: A Comprehensive Review and more Exercises Computer Numerical Control in PDF only on Docsity!

HTTP Status Code:A Comprehensive Reviews 2025

100 Continue - ansThis means that the server has received the request headers, and that the client should proceed to send the request body. 101 Switching Protocols - ansThis means the requester has asked the server to switch protocols and the server is acknowledging that it will do so. 1xx Informational - ansRequest received, continuing process. This class of status code indicates a provisional response, consisting only of the Status-Line and optional headers, and is terminated by an empty line. Since HTTP/1.0 did not define any 1xx status codes, servers must not send a 1xx response to an HTTP/1.0 client except under experimental conditions. 200 OK - ansStandard response for successful HTTP requests. The actual response will depend on the request method used. In a GET request, the response will contain an entity corresponding to the requested resource. In a POST request the response will contain an entity describing or containing the result of the action. 201 Created - ansThe request has been fulfilled and resulted in a new resource being created. 202 Accepted - ansThe request has been accepted for processing, but the processing has not been completed. The request might or might not eventually be acted upon, as it might be disallowed when processing actually takes place 203 Non-Authoritative Information (since HTTP/1.1) - ansThe server successfully processed the request, but is returning information that may be from another source. 204 No Content - ansThe server successfully processed the request, but is not returning any content. 205 Reset Content - ansThe server successfully processed the request, but is not returning any content. Unlike a 204 response, this response requires that the requester reset the document view. 206 Partial Content - ansThe server is delivering only part of the resource due to a range header sent by the

client. The range header is used by tools like wget to enable resuming of interrupted downloads, or split a download into multiple simultaneous streams. 2xx Success - ansThis class of status codes indicates the action requested by the client was received, understood, accepted and processed successfully. 300 Multiple Choices - ansIndicates multiple options for the resource that the client may follow. It, for instance, could be used to present different format options for video, list files with different extensions, or word sense disambiguation. 301 Moved Permanently - ansThis and all future requests should be directed to the given URI. 302 Found - ansThis is an example of industry practice contradicting the standard. The HTTP/1. specification (RFC 1945) required the client to perform a temporary redirect (the original describing phrase was "Moved Temporarily"), 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. However, some Web applications and frameworks use the 302 status code as if it were the 303. 303 See Other - ansThe response to the request can be found under another URI using a GET method. When received in response to a POST (or PUT/DELETE), it should be assumed that the server has received the data and the redirect should be issued with a separate GET message. 304 Not Modified - ansIndicates the resource has not been modified since last requested. Typically, the HTTP client provides a header like the If-Modified-Since header to provide a time against which to compare. Using this saves bandwidth and reprocessing on both the server and client, as only the header data must be sent and received in comparison to the entirety of the page being re-processed by the server, then sent again using more bandwidth of the server and client. 305 Use Proxy (since HTTP/1.1) - ansMany HTTP clients (such as Mozilla and Internet Explorer) do not correctly handle responses with this status code, primarily for security reasons. 306 Switch Proxy - ansNo longer used. Originally meant "Subsequent requests should use the specified proxy." 307 Temporary Redirect (since HTTP/1.1) - ansIn this case, the request should be repeated with another

406 Not Acceptable - ansThe requested resource is only capable of generating content not acceptable according to the Accept headers sent in the request. 407 Proxy Authentication Required - ansThe client must first authenticate itself with the proxy. 408 Request Timeout - ansThe server timed out waiting for the request. According to W3 HTTP specifications: "The client did not produce a request within the time that the server was prepared to wait. The client MAY repeat the request without modifications at any later time." 409 Conflict - ansIndicates that the request could not be processed because of conflict in the request, such as an edit conflict.[2] 410 Gone - ansIndicates that the resource requested is no longer available and will not be available again. This should be used when a resource has been intentionally removed and the resource should be purged. Upon receiving a 410 status code, the client should not request the resource again in the future. Clients such as search engines should remove the resource from their indices. Most use cases do not require clients and search engines to purge the resource, and a "404 Not Found" may be used instead. 411 Length Required - ansThe request did not specify the length of its content, which is required by the requested resource.[2] 412 Precondition Failed - ansThe server does not meet one of the preconditions that the requester put on the request.[2] 413 Request Entity Too Large - ansThe request is larger than the server is willing or able to process. 414 Request-URI Too Long - ansThe URI provided was too long for the server to process. 415 Unsupported Media Type - ansThe request entity has a media type which the server or resource does not support.[2] For example, the client uploads an image as image/svg+xml, but the server requires that images use a different format. 416 Requested Range Not Satisfiable - ansThe client has asked for a portion of the file, but the server cannot supply that portion.[2] For example, if the client asked for a part of the file that lies beyond the end

of the file.[2] 417 Expectation Failed - ansThe server cannot meet the requirements of the Expect request-header field. 418 I'm a teapot (RFC 2324) - ansThis code was defined in 1998 as one of the traditional IETF April Fools' jokes, in RFC 2324, Hyper Text Coffee Pot Control Protocol, and is not expected to be implemented by actual HTTP servers. 4xx Client Error - ansThe 4xx class of status code is intended for cases in which the client seems to have erred. Except when responding to a HEAD request, the server should include an entity containing an explanation of the error situation, and whether it is a temporary or permanent condition. These status codes are applicable to any request method. User agents should display any included entity to the user. 500 Internal Server Error - ansA generic error message, given when no more specific message is suitable. 501 Not Implemented - anshe server either does not recognize the request method, or it lacks the ability to fulfill the request.[2] 502 Bad Gateway - ansThe server was acting as a gateway or proxy and received an invalid response from the upstream server.[2] 503 Service Unavailable - ansThe server is currently unavailable (because it is overloaded or down for maintenance). Generally, this is a temporary state. 504 Gateway Timeout - ansThe server was acting as a gateway or proxy and did not receive a timely response from the upstream server.[2] 505 HTTP Version Not Supported - ansThe server does not support the HTTP protocol version used in the request. 506 Variant Also Negotiates (RFC 2295) - ansTransparent content negotiation for the request results in a circular reference.