Why does HTTP 404?

Question

When I go search the net knowing these sites are available as I have visited them not more than a day ago HTTP 404 tells me the location is not found. Where do I go too from there?

Answer 1

You're out of luck. Those pages are gone now.

Answer 2

CAUSE

The Web server returns the "HTTP 404 - File not found" error message when it cannot retrieve the page that was requested.



The following are some common causes of this error message:

• The requested file has been renamed.

• The requested file has been moved to another location and/or deleted.

• The requested file is temporarily unavailable due to maintenance, upgrades, or other unknown causes.

• The requested file does not exist.

• IIS 6.0: The appropriate Web service extension or MIME type is not enabled.

• A virtual directory is mapped to the root of a drive on another server.



Back to the top

RESOLUTION

To resolve this problem, verify that the file requested in the browser's URL exists on the IIS computer and that it is in the correct location.



Use the IIS Microsoft Management Console (MMC) snap-in to determine where the file requested must exist in the IIS computer's file system.



This is particularly important if the Web site uses a virtual directory (VDIR). A VDIR is a directory that is not contained in the home directory of the Web site, but appears to client browser as though it does. This virtual directory must be mapped to a subfolder on a drive or reference the files by name.



For example, assume that the URL that caused the 404 error is http://Microsoft.Com/Test/File1.htm, and the IIS snap-in shows that for Microsoft.Com Web site, the /Test/ directory is actually a virtual directory that maps to the location of c:\Information on the IIS computer. This means that you must verify that the File1.htm file is located in the c:\Information directory (and that the file name is spelled correctly).



IIS6 Dynamic Content: A 404.2 entry in the W3C Extended Log file is recorded when a Web Extension is not enabled. Use the IIS Microsoft Management Console (MMC) snap-in to enable the appropriate Web extension. Default Web Extensions include: ASP, ASP.net, Server-Side Includes, WebDAV publishing, FrontPage Server Extensions, Common Gateway Interface (CGI). Custom extensions must be added and explicitly enabled. See the IIS 6.0 Help File for more information.

IIS6 Static Content: A 404.3 entry in the W3C Extended Log file is recorded when an extension is not mapped to a known extention in the MIME Map property. Use the IIS Microsoft Management Console (MMC) snap-in to configure the appropriate extension in the MIME Map. See the IIS 6.0 Help file for more information.



For more information about other, less common causes of this error message, click the following article numbers to view the articles in the Microsoft Knowledge Base:

247714 (http://support.microsoft.com/kb/247714/) Using PUT command for a long file name causes "HTTP 404 - File not found" error

221553 (http://support.microsoft.com/kb/221553/) Setting file attributes on Web content causes 404 - File not found error

216803 (http://support.microsoft.com/kb/216803/) IIS hidden static files return HTTP 404 or access denied errors

288123 (http://support.microsoft.com/kb/288123/) HTTP Error 404 "Page cannot be displayed" when you attempt to connect to the OWA server after you upgrade from Exchange Server 5.5 to Exchange 2000 Server



http://support.microsoft.com/kb/248033

Answer 3

If it's a 404, then your machine HAS connected to the server, but the page you want is no longer on that server. You may be able to find a cache version of it on google.

Answer 4

It means that your PC cannot contact with the server, its likely you will just have to wait until the site fixes its problems

Answer 5

it could be as simple of a problem as not having the trailing / since the page you think your accessing is a directory with an index.html file

Answer 6

Have a look at this



http://www.helpwithpcs.com/courses/html/html_http_status_codes.htm