aspnet_filter.dll 260个字符网址限制 [英] aspnet_filter.dll 260 character url path limit

查看:88
本文介绍了aspnet_filter.dll 260个字符网址限制的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

大家好,

Hi Everybody,

我似乎正在考虑出现的问题成为.NET Web开发人员的常见问题。这是url路径的奇怪的260个字符限制。

I seem to be butting my head into what appears to be a common problem amongst .NET Web developers.  That is the bizarre 260 character limit for url paths. 

当使用Request.PathInfo变量时,这成为一个真正的问题,因为pathinfo中的信息可能相当很长(无论如何都超过260个字符)。这是一个完全合法的路径字符串,实际上适用于IIS 5和6中的其他mime类型(即:通过将文件扩展名从.aspx更改为其他内容),因此它显然不是IIS限制。此外,它显然不是.NET框架的核心限制,因为长路径在Visual Studio 2005附带的ASP.NET开发服务器中运行良好。因此,这使我得出结论,问题必须在aspnet_filter.dll ISAPI过滤器中.NET。

This becomes a real issue when using the Request.PathInfo variable, because the information in the pathinfo could be quite long (more than 260 characters at any rate).  This is a perfectly legitimate path string, and actually works for other mime types in IIS 5 and 6 (ie: by changing the file extension from .aspx to something else), so it's clearly not an IIS limitation.  Also, it is clearly not a core .NET framework limitation because the long path works fine in the ASP.NET development server included with Visual Studio 2005.  So this leads me to conclude that the problem must be in the aspnet_filter.dll ISAPI filter for .NET.

最糟糕的情况是,如果路径长度限制真的像某些开发人员建议的那样硬编码,我假设我可以反汇编DLL并替换硬编码值,除非它被某种加密模糊了。即使这样,我也可以在机器代码中的解密算法之后添加一个MOV语句。

Worst case scenario, if the path length limit really is hardcoded like some developers have suggested, I suppose I could disassemble the DLL and replace the hardcoded value, unless of course it's obscured with some sort of encryption.  Even then, I could add a MOV statement after the decryption algorithm in the machine code. 

然而,鉴于.NET架构师和工程师的强大实力,我非常怀疑这样一个无耻的严重限制是以如此激烈的方式施加的,或者更糟糕的是,对这种程度进行了明显的监督。

However, given the impressive prowess of the .NET architects and engineers, I seriously doubt that such a brazen and crippling limitation was imposed in such a drastic way, or worse yet, that a glaring oversight of this magnitude was made.

所以我发出一个询问...是否有人知道如何改变这个毁灭性的260个字符限制?我已经在注册表中尝试了UrlSegmentMaxLength设置无济于事。我使用的是IIS 5/6和.NET 2.0.50727。

So I send out an enquiry... is there anyone who knows how to change this devastating 260 character limit?  I have already tried the UrlSegmentMaxLength setting in the registry to no avail.  I am using IIS 5/6 and .NET 2.0.50727.

任何线索?


谢谢,

Drew Mcpherson

Drew Mcpherson

Bine Consulting Corp。

Bine Consulting Corp.

推荐答案

尝试更改为起诉类似

Try to change to sue something like

原始URI: http://www.domain .com /?id = 12& data = safgasfd

最终网址: http://www.domain.com/12/safgasfd

我不知道它是如何调用的,但许多.net博客都使用此功能....

I don't know how it's is called, but many .net blogs use this feature....


这篇关于aspnet_filter.dll 260个字符网址限制的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆