Activity › Forums › Salesforce® Discussions › HTTP status codes
-
HTTP status codes
Posted by chanchal kumar on September 5, 2018 at 2:31 PMWhat are HTTP status codes? Enlist few with meaning.
Pooja replied 6 years, 2 months ago 6 Members · 5 Replies -
5 Replies
-
Hi Chanchal,
HTTP status codes basically are the representation of the status of the task that has been performed on the server, with the mode of some codes. Every code has their own meaning.
Some of the HTTP status codes with their meaning are as follows:
Code 200: This indicates success.
Code 201: This indicates resource has been successfully created.
Code 204: This indicates that there is no content in the response body.
Code 404: This indicates that there is no method available.
There are few more such codes that indicate the status.Thanks.
- [adinserter block='9']
-
Hi Chanchal,
HTTP status codes are standard response codes given by web site servers on the internet. The codes help identify the cause of the problem when a web page or other resource does not load properly.
HTTP status codes are sometimes called browser error codes or internet error codes.
For example, the HTTP status line 500: Internal Server Error is made up of the HTTP status code of 500 and the HTTP reason phrase of Internal Server Error.
Thanks.
-
Hi Chanchal,
The Status-Code element in a server response, is a 3-digit integer where the first digit of the Status-Code defines the class of response and the last two digits do not have any categorisation role. Some examples are:
- 1xx: Informational: It means the request has been received and the process is continuing.
- 2xx: Success: It means the action was successfully received, understood, and accepted.
- 3xx: Redirection: It means further action must be taken in order to complete the request.
- 4xx: Client Error: It means the request contains incorrect syntax or cannot be fulfilled.
- 5xx: Server Error: It means the server failed to fulfill an apparently valid request.
Thank You.
-
Hi Chanchal,
HTTP Status Codes
This page is created from HTTP status code information found at ietf.org and Wikipedia. Click on the category heading or the status code link to read more.1xx Informational
100 Continue
101 Switching Protocols
102 Processing (WebDAV)
2xx Success
200 OK
201 Created
202 Accepted
203 Non-Authoritative Information
204 No Content
205 Reset Content
206 Partial Content
207 Multi-Status (WebDAV)
208 Already Reported (WebDAV)
226 IM Used
3xx Redirection
300 Multiple Choices
301 Moved Permanently
302 Found
303 See Other
304 Not Modified
305 Use Proxy
306 (Unused)
307 Temporary Redirect
308 Permanent Redirect (experimental)
4xx Client Error
400 Bad Request
401 Unauthorized
402 Payment Required
403 Forbidden
404 Not Found
405 Method Not Allowed
406 Not Acceptable
407 Proxy Authentication Required
408 Request Timeout
409 Conflict
410 Gone
411 Length Required
412 Precondition Failed
413 Request Entity Too Large
414 Request-URI Too Long
415 Unsupported Media Type
416 Requested Range Not Satisfiable
417 Expectation Failed
418 I’m a teapot (RFC 2324)
420 Enhance Your Calm (Twitter)
422 Unprocessable Entity (WebDAV)
423 Locked (WebDAV)
424 Failed Dependency (WebDAV)
425 Reserved for WebDAV
426 Upgrade Required
428 Precondition Required
429 Too Many Requests
431 Request Header Fields Too Large
444 No Response (Nginx)
449 Retry With (Microsoft)
450 Blocked by Windows Parental Controls (Microsoft)
451 Unavailable For Legal Reasons
499 Client Closed Request (Nginx)
5xx Server Error
500 Internal Server Error
501 Not Implemented
502 Bad Gateway
503 Service Unavailable
504 Gateway Timeout
505 HTTP Version Not Supported
506 Variant Also Negotiates (Experimental)
507 Insufficient Storage (WebDAV)
508 Loop Detected (WebDAV)
509 Bandwidth Limit Exceeded (Apache)
510 Not Extended
511 Network Authentication Required
598 Network read timeout error
599 Network connect timeout error
Hope this helps.
-
The response header contains an HTTP status code. If the response isn’t successful, the response body contains an error message, and if appropriate, information about the field or object where the error occurred.
200
Success with GET, PATCH, or HEAD request
201
Success with POST request
204
Success with DELETE
400
The request could not be understood, usually because the ID is not valid for the particular resource. For example, if you use a userId where a groupId is required, the request returns 400.
Log In to reply.