tag:blogger.com,1999:blog-3531969847869413627.post8955071723786675159..comments2023-07-05T07:05:39.753-04:00Comments on Boduch's Blog: Consistent HTTP CodesAdam Boduchhttp://www.blogger.com/profile/00484502507931628726noreply@blogger.comBlogger1125tag:blogger.com,1999:blog-3531969847869413627.post-25795223006274615572010-03-26T22:29:13.538-04:002010-03-26T22:29:13.538-04:00403 means that the resource exists but the user is...403 means that the resource exists but the user is not authorized to use it. Examples of this include directory listings (which do exist when permitted by the server, and are forbidden if not (implied: do exist)).<br />404 means that the resource just isn't there.<br /><br />Giving off false http codes is never a good thing. Most browsers (and not to mention web crawlers) are designed to react a certain way to a certain reply. Messing with that will give your users the wrong idea.<br /><br />You COULD tell your server to send a 404 on a directory listing, but then that implies that the directory doesn't exist, and that no files may be requested from that directory.<br /><br />It's always safest to go with the specs. And the HTTP spec is pretty much tried and tested.Tor Valamohttp://stackoverflow.comnoreply@blogger.com