使用404 htaccess重定向进行验证

There is no such thing as 404 redirection. HTTP code 404 means that the requested resource is not available. It would be incorrect for a client to treat it otherwise.

然后不要这样做。 （我们真的不知道你在做什么细节，但很明显这是错的。）你不知道我在做什么，但是你知道这是错的吗？凉。 我的.htaccess文件是这样的： ErrorDocument 404 /script.php 每当你请求一个不存在的页面时，你的请求由'/'脚本处理.PHP'。它有效 - 例如，查看 www.safetycam.pl 。 难怪你遇到了问题。 404表示未找到。 ErrorDocument指令允许您向用户显示 一个有吸引力的人类可读页面，用于未找到。消息。 这仍然是一个错误，这就是为什么它被称为* ErrorDocument * ，消息是未找到。 当然，那些自定义404文档的人经常会验证它，但是他们会在*指向ErrorDocument 之前这样做。

Then don''t do that. (We don''t really know what you do in detail, but it is pretty clear that it''s wrong.) You don''t know what I''m doing, but you know it''s wrong? Cool. My .htaccess file is like this: ErrorDocument 404 /script.php Every time you request a page that is not there, your request is handled by the ''script.php''. It works - check out www.safetycam.pl, for example. Little wonder you are having problems. 404 means "Not found." The ErrorDocument directive allows you present the user with an attractive human-readable page for the "Not found" message. It is still an Error which is why it is called *ErrorDocument* and the message is "Not found." Of course people who do customize their 404 document often do validate it, but they do so *before* pointing ErrorDocument at it.

浏览器是众所周知的有错误。

Browsers are known to have bugs.

正确 - 所以请致电Mozilla和Firefox的人，告诉他们他们的浏览器有一个严重的错误:)（和微软，课程） 当然，这个错误存在于你的大脑中。无论你拥有什么？ 认为404不是错误？ 但是当我尝试验证页面时出现404错误 - 其中<令我感到困惑，因为我认为Apache在内部进行了重定向而没有向客户端发送错误消息。你做到了吗？好吧，我们知道发生了什么事的可能性更小，因为你没有透露URL，更不用说明你在.htaccess 文件中显示的内容了。

Right - so please call the Mozilla and Firefox guys, tell them their browsers have a serious bug :) (and Microsoft, of course) The bug, of course, is in your brain. Whatever possessed you to think that 404 was anything other than an error? but when I try to validate the page I get a 404 error - which bewilders me, because I thought Apache does the redirection internally without sending the error message to the client. You did? Well, we have even less odds of knowing what''s going on, since you don''t reveal the URL, still less show what you have in the .htaccess file.

我做了，但我想我知道我的错误是什么：我的猜测是将404 与ErrorDocument信息一起发送给客户端，然后<客户端发送另一个请求ErrorDocument的请求，附加了初始请求 - 而我最初认为是Apache本身使用该指令来处理请求。如果我的猜测是正确的，那对我来说将是一个非常坏的消息：（

Yes I did, but I think I know what was my mistake: my guess is that the 404 is sent to the client together with the ErrorDocument information, then the client sends another request asking for ErrorDocument, attaching the initial request - while I initially thought that it is Apache itself that uses the directive to handle the request. If my guess is right, that would be a VERY bad news for me :(

Apache发送404然后发送文件会发生什么。 导致许多代理商，尤其是搜索蜘蛛等机器人，以及 ，如您所发现的，验证机器人当场注销。 毕竟ErrorDocument的想法是为人类提供一个人类可读的线索，告诉他们发生了什么 - 如果一个人没有操作就毫无意义客户端。 Apache向自己发送404没有任何意义。它知道 文件不存在。它不能替代ErrorDocument 是一个不存在的文件，但只能用它替换它自己的 内置而非普通的错误文档。 - Lars Eighner ei*****@io www.io/~eighner/ 拯救热带雨林！吃素食！

What happens is Apache sends 404 and then the document. The 404 causes many agents, especially bots such as search spiders and, as you have discovered, validation bots to sign off on the spot. The idea of the ErrorDocument after all is to provide the human with a human-readable clue as to what has happened - something that is pointless if a human is not operating the client. There is no point in Apache sending 404 to itself. It knows the document isn''t there. It does not substitute the ErrorDocument for a non-existing document, but only substitutes it for its own built-in rather plain not-found-error document. -- Lars Eighner ei*****@io www.io/~eighner/ Save the Rainforest! Eat a vegetarian!