Pages

HTTP Errors and Success Details on the Web

While we surfing on the internet and browsing websites, sometimes we saw some HTTP bad errors like 404 Not Found (one of the most popular bad errors in the internet), we don't know why this bad errors came and shown instead of certain websites which we are looking for, here i described a complete list of HTTP bad errors, this will help you to find out the problems of that website.

HTTP : Hyper Text Transfer Protocol

HTTPs : Hyper Text Transfer Protocol Secure (Over Secure Connection)

1. 1xx Informational : Starting with 1code means request is accepted and processing
2. 101 Switiching Protocols : Person requests to server for protocol switch and server response this
3. 102 Processing  (webDAV) (RFC 2518) : Server is accepted request and in progress but no response
4. 2xx Success : Request is accepted, permitted and processing successfully
5. 200 OK : Successful response for a HTTP requests
6. 201 Created : Request is accepted and making a new resources
7. 202 Accepted : Request is accepted for processing but processing is not completed yet
8. 203 Non-Authoritative Information (Since HTTP/1.1) : Server accepted request successfully but the information might came from another unknown source
9. 204 No Content :  Server accepted request successfully but no content
10. 205 Reset Content :  Server accepted request successfully but no content, might different from 204 Code response request to reset document view to its user
11. 206 Partial Content : It has been used by wgt tools for download
12. 207 Multi-Status (WebDAV) (RFC 2518) : It means the message body is xml which can contain different response code for different sub-requests
13. 3xx Redirection : This code means to make this request complete, client must redirect
14. 301 Moved Permanently : It means current and future all request will be redirect
15. 302 Found : Most popular redirect code but not accepted by Industrial Practice which is disagree Standerd Rules
16. 303 See Other (Since HTTP/1.1) : Response request will found another url by GET method
17. 304 Not Modified : Request was not modified after last request
18. 305 Use Proxy (Since HTTP/1.1) : For primary security reason many HTTP clients like Mozilla and Internet Explorer not response right way by this status code
19. 306 Switch Proxy (Since HTTP/1.1) : Is not using anymore
20. 307 Temporary Redirect (Since HTTP/1.1) : Have to make re-request by another URI for this code, can be compared with 303
21. 4xx Client Error : This code used when client make a mistake
22. 400 Bad Request : This code means mistakes in requests
23. 401 Unauthorized : Like 403 Forbidden but only authentication cant be success
24. 402 Payment Required : Saved for future usages, not have been used yet
25. 403 Forbidden : Request was legal but server denied this response for the requests
26. 404 Not Found : Resources cant be found at this moment but it can found in future
27. 405 Method Not Allowed : This resource request is not supported by resource, as a example this code is shown if use GET method where need POST method
28. 406 Not Acceptable : Requested resource can make only that content which is sent with request but not acceptable following Accept Headers
29. 408 Request Timeout : Sever time has been out when waiting for the requests
30. 409 Conflict : Request cant be completed because Conflict remain in the request, e.g: Edit-conflict
31. 410 Gone : Resources cant be found at this moment but it cant be found in future also
32. 411 Length Required : Content length is not attached with request, which is usable for requested resource
33. 412 Precondition Failed :  It means a past-condition was not followed by the request resources
34. 413 Request Entity Too Large : Request is too much where server can not take it
35. 414 Request-URI Too Long : URI is too long for server
36. 415 Unsupported Media Type : Sending media file request is not supported by server
37. 416 Requested Range Not Satisfiable : Request fore a part of a file but server can not supply that certain part
38. 417 Expectation Failed : Expect request-header field is not matched with server
39. 418 I'm a teapot : HTCPCP server is teapot, IETF April Fool's jokes as RFC 2324, Hyper Text Coffee Port Control Protocol
40. 422 Unprocessable Entity (WebDAV) (RFC 4918) : Request was right but can not be follow for meaning
41. 423 Locked (WebDAV) (RFC 4918) : Resources followed but it is locked
42. 424 Failed Dependency (WebDAV) (RFC 4918) : It means request failed for pre-request was failed
43. 425 Unordered Collection (RFC 3648) : It can be found in "WebDAV Advance Collections Protocol" but it cant be found in "Web Distributed Authoring and Versioning (WebDAV) Orderd Collections Protocol"
44. 426 Upgrade Required (RFC 2817) : It means client have to another protocol switch like TLS/1.0
45. 449 Retry With : It indicate a extension of Microsoft and it means make a re-request after successful work
46. 450 Blocked by Windows Parental Controls : It also indicate a extension of Microsoft, this code is shown when windows parental control is on and requested webpage access is being closed
47. 5xx Server Error : These codes shown when server failed to make a valid request
48. 500 Internal Server Error : When server can not find a reason for the problem created
49. 501 Not Implemented : Server is not understand the request method or it is not able to fulfill of requests
50. 502 Bad Gateway : Sever was worked as a gateway or proxy and a invalid response from down stream server
51. 503 Service Unavailable : Server is closed at this moment and it used for temporary condition
52. 504 Gateway Timeout : Sever was worked as a gateway or proxy and failed to take request in time from down stream server
53. 505 HTTP Version Not Supported : HTTP Protocol Version is not supported by server
54. 506 Variant Also Negotites (RFC 2295) : Circle reference is created for the request following transparent content-negotiation
55. 507 Insufficient Storage (WebDAV) (RFC 4918) : Not enough storage to for the requests
56. 509 Bandwith Limit Exceeded (Apache bw/limited extension) : Expected bandwidth for the server is not located in RFCs to complete the request
57. 510 Not Extended (RFC 2774) : Need extended extension for the server to complete the request

Courtesy : http://www.earnhelp.com (Translated and Modified a little bit for the Visitors)

No comments:

Post a Comment

http://www.bd69ctg.blogspot.com