Basically 404 is a Not Found status code.
He is the example flow:
User inputs https://answersrip.com/question/index?qid=20080513093749AAWrUPa&show=7
Web Browser sends:
GET /question/index;_ylt=Ar.aVjzeYbLkcWD.s9IGVYDsy6IX;_ylv=3? HTTP/1.1
Host: answers.yahoo.com
To Resolved IP: 209.73.187.220 (from ISP's DNS) 209.73.187.220
-
Server responds with (if server/object/file/page found):
HTTP/1.1 200 OK
Date: Mon, 15 May 2008 20:16:34 GMT
Server: Server Type (Server OS Family Type) (Server OS Type)
Last-Modified: Thurs, 05 May 2008 08:15:55 GMT
Etag: "some1-num-2ber0003"
Accept-Ranges: bytes
Content-Length: 999
Connection: close
Content-Type: text/html; charset=UTF-8
Some page text
-
Server responds (if server/object/file/page found):
HTTP/1.1 404 Object Not Found
-This is optional:
HTTP/1.1 404 Object Not Found
Date: Mon, 15 May 2008 20:16:35 GMT
Server: Server Type (Server OS Family Type) (Server OS Type)
Last-Modified: Thurs, 05 May 2008 08:15:56 GMT
Etag: "some1-num-2ber0013"
Accept-Ranges: bytes
Content-Length: 999
Connection: close
Content-Type: text/html; charset=UTF-8
Custom server error page!
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
############################################
Hi Mike.
Just a little notice.
I know HTTP 1.1 brought relevance but when the inventor of HTTP and its status codes, Tim Berners-Lee of the World Wide Web Consortium (W3C).
The HyperText Transfer Protocol daemon (HTTPd) was the world's first web server and HTTP web server.
He did NOT say 40x is a group.
There are hidden requests behind the codes, FTP, SMTP, POP and more. Those codes were saved from them, along time ago it was all TELe communications NETwork and Disk Operating Systems. All through, usually back then it was through one port in small systems, thats why they used protocols, otherwise they might as well called them ports. Nowadays we use protocols on seperate ports and error codes were seperated to different protocols. Leaving a bunch of numbers that didn’t mean a thing to each other in sequence.
Just since 1.1 came out they added relevance to the codes.
Thanks.
By CybX Systems - ASP.NET MVP
Here is a good list of HTTP status codes of 1.1:
10.1 Informational 1xx
10.1.1 100 Continue
10.1.2 101 Switching Protocols
10.2 Successful 2xx
10.2.1 200 OK
10.2.2 201 Created
10.2.3 202 Accepted
10.2.4 203 Non-Authoritative Information
10.2.5 204 No Content
10.2.6 205 Reset Content
10.2.7 206 Partial Content
10.3 Redirection 3xx
10.3.1 300 Multiple Choices
10.3.2 301 Moved Permanently
10.3.3 302 Found
10.3.4 303 See Other
10.3.5 304 Not Modified
10.3.6 305 Use Proxy
10.3.7 306 (Unused)
10.3.8 307 Temporary Redirect
10.4 Client Error 4xx
10.4.1 400 Bad Request
10.4.2 401 Unauthorized
10.4.3 402 Payment Required (Future versions od HTTP)
10.4.4 403 Forbidden
10.4.5 404 Not Found
10.4.6 405 Method Not Allowed
10.4.7 406 Not Acceptable
10.4.8 407 Proxy Authentication Required (401 for proxies)
10.4.9 408 Request Timeout
10.4.10 409 Conflict
10.4.11 410 Gone
10.4.12 411 Length Required
10.4.13 412 Precondition Failed
10.4.14 413 Request Entity Too Large
10.4.15 414 Request-URI Too Long
10.4.16 415 Unsupported Media Type
10.4.17 416 Requested Range Not Satisfiable
10.4.18 417 Expectation Failed
10.5 Server Error 5xx
10.5.1 500 Internal Server Error
10.5.2 501 Not Implemented
10.5.3 502 Bad Gateway
10.5.4 503 Service Unavailable
10.5.5 504 Gateway Timeout
10.5.6 505 HTTP Version Not Supported (Old or New version of HTTP protocol negotiating required).
############################################
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~