maxRequestPathLength不是ASP.NET 4文档中并不起作用 [英] maxRequestPathLength not in ASP.NET 4 documentation and doesn't work

查看:315
本文介绍了maxRequestPathLength不是ASP.NET 4文档中并不起作用的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

如果我试图在ASP.NET应用程序以使用新的maxRequestPathLength设置,这是行不通的。我得到一个无法识别的属性错误。我同时使用ASP.NET集成和IIS 7经典应用程序池尝试什么也搞笑的是,如果你搜索maxRequestPathLength在MSDN上它是没有在文档中被发现,其中除了对ASP的新功能列表.NET 4怎么办?

If I try to use the new maxRequestPathLength settings in an ASP.NET application it does not work. I get an unrecognized attribute error. I've tried using both ASP.NET Integrated and Classic application pools in IIS 7. What is also funny is that if you search for maxRequestPathLength on MSDN it is no where to be found in the documentation except in the list of new features for ASP.NET 4. What gives?

推荐答案

显然,这个设置名字被更改,并移动到下的注册表HKEY_LOCAL_MACHINE \\系统\\ CurrentControlSet \\服务\\ HTTP \\参数。名称是UrlSegmentMaxLength。默认值是260。这种特殊的设置限制的字符允许在网址的每个路径段的量。在 http://stackoverflow.com/questions ,问题将是一个路径段。

Apparently this setting name was changed and move to the registry under "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\HTTP\Parameters." The name is UrlSegmentMaxLength. The default value is 260. This particular setting limits the amount of characters allowed in each path segment of a URL. In http://stackoverflow.com/questions, "questions" would be a path segment.

该文档可在Microsoft知识库文章中找到关于 HTTP.SYS注册表设置

Documentation for this can be found in the Microsoft knowledge base article on http.sys registry settings.

这篇关于maxRequestPathLength不是ASP.NET 4文档中并不起作用的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

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