On 9 May 2001, at 11:15, Nick McClure wrote:
> You should be able to check CFHTTP.StatusCode
>
> this will be equal to 404 or 500.
>
> 200 is a successful request.
Yes, that's the way it's supposed to work. Unfortunately, a
bunch of people out there have configured their servers to
return status 200 even for requests for nonexistent pages. It
makes things hard for spider writers, and results in clutter
for search-engine databases.
Some of these server admins do it to avoid having their custom
404 pages hidden by IE's damned "friendly" error messages.
Regardless of the reason, it's a bad idea and yet another bit
of Microsoftian damage to the idea of standards. A better way
to do avoid IE's interference is to make sure the custom page
contents are longer than 512 (or maybe it's 1024) bytes.
I think that requests for nonexistent .cfm files result in
status 200 for the usual configuration of IIS as well, so that
could be another contribution to the problem.
Keith C. Ivey <[EMAIL PROTECTED]>
Webmaster, EEI Communications
66 Canal Center Plaza, Suite 200
Alexandria, VA 22314
Telephone: 703-683-0683
Fax: 703-683-4915
Web Site: http://www.eeicommunications.com
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
