PRB: Self-Referencing Dynamic Web Pages That Mask 404 Errors Can Cause Loop in Content Analyzer (281749)
The information in this article applies to:
- Microsoft Site Server 3.0
This article was previously published under Q281749 IMPORTANT: This article contains information about modifying the registry. Before you
modify the registry, make sure to back it up and make sure that you understand how to restore
the registry if a problem occurs. For information about how to back up, restore, and edit the
registry, click the following article number to view the article in the Microsoft Knowledge Base:
256986 Description of the Microsoft Windows Registry
SYMPTOMS
When you use Content Analyzer to crawl a Web site that uses Allaire ColdFusion, you must add a registry key and value so that Content Analyzer recognizes the ColdFusion (.cfm) pages. After you add the registry key and value, when you try to crawl the Web site, the crawl does not stop, and the page count for the Web site exceeds the number of physical pages.
CAUSE
ColdFusion does not return an HTTP 404 "File not found" error when a page is not found. In addition, if the generic page that is returned references another broken link, Content Analyzer follows this broken link, which creates a loop.
RESOLUTION
To resolve this problem, configure ColdFusion to return an HTTP 404 error with the error page. This informs Content Analyzer that the page doesn't exist. If you do not configure ColdFusion to return an HTTP 404 error, there is no way to find the broken links.
WORKAROUND
To work around this problem, correct the reference to the broken link on the 404 error page that ColdFusion returns.
Modification Type: | Major | Last Reviewed: | 6/11/2002 |
---|
Keywords: | kbDSupport kbprb KB281749 |
---|
|