HTTP Error 404.11 - Not Found

The request filtering module is configured to deny a request that contains a double escape sequence.

Most likely causes:

  • The request contained a double escape sequence and request filtering is configured on the Web server to deny double escape sequences.

Things you can try:

  • Verify the configuration/system.webServer/security/requestFiltering@allowDoubleEscaping setting in the applicationhost.config or web.confg file.

Detailed Error Information:

Module   RequestFilteringModule
Notification   BeginRequest
Handler   ExtensionlessUrlHandler-Integrated-4.0
Error Code   0x00000000
Requested URL   http://www.bestmyself.net:80/zh/tag/%E9%9D%92%E8%89%B2%E7%BB%84%E7%BB%87%EF%BC%8C%E8%87%AA%E7%94%B1%E4%BC%81%E4%B8%9A%EF%BC%8C%E6%89%98%E6%96%AF%E5%8D%A1%E7%BA%B3%EF%BC%8C%E9%99%AA%E4%BC%B4/
Physical Path   D:\inetpub\wwwroot\zh\tag\%E9%9D%92%E8%89%B2%E7%BB%84%E7%BB%87%EF%BC%8C%E8%87%AA%E7%94%B1%E4%BC%81%E4%B8%9A%EF%BC%8C%E6%89%98%E6%96%AF%E5%8D%A1%E7%BA%B3%EF%BC%8C%E9%99%AA%E4%BC%B4\
Logon Method   Not yet determined
Logon User   Not yet determined
Request Tracing Directory   D:\LogFiles\FailedReqLogFiles

More Information:

This is a security feature. Do not change this feature unless the scope of the change is fully understood. You should take a network trace before changing this value to confirm that the request is not malicious. If double escape sequences are allowed by the server, modify the configuration/system.webServer/security/requestFiltering@allowDoubleEscaping setting. This could be caused by a malformed URL sent to the server by a malicious user.

View more information »