HTTP 400:在 URL 中检测到无效字符.IIS解码URL太早?这里发生了什么?

HTTP 400 : detected invalid characters in the URL. IIS decoding URL too early? Whats going on here?(HTTP 400:在 URL 中检测到无效字符.IIS解码URL太早?这里发生了什么?)

本文介绍了HTTP 400:在 URL 中检测到无效字符.IIS解码URL太早?这里发生了什么?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

So i have this URL: http://test.com/afolder/who-else-wants-to-make-horror-movies%3f/

which is URL encoded version of : http://test.com/afolder/who-else-wants-to-make-horror-movies?/

But IIS7 throws a 400:

HTTP Error 400.0 - Bad Request ASP.NET detected invalid characters in the URL.

But why is it doing that if i have correctly encoded the URL?

I'm also having the same issue with other URL encoded chars like '/' which is '%2f' but when .net resolves the handler it does so after decoding the URL which then changes the effective path, grrrr.

解决方案

Looks like there are some issues with IIS7 on x64....not sure if this is your issue or not:

http://blogs.iis.net/rakkimk/archive/2008/10/10/asp-net-2-0-x64-you-may-get-http-400-bad-request-or-error-as-mentioned-in-kb-932552-or-826437.aspx

这篇关于HTTP 400:在 URL 中检测到无效字符.IIS解码URL太早?这里发生了什么?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持编程学习网!

本文标题为:HTTP 400:在 URL 中检测到无效字符.IIS解码URL太早?这里发生了什么?

基础教程推荐