asp.net 1.1 和 Firefox 7
我们有一些旧的内部应用程序是用 asp.net 1.1 编写的。由于各种原因，它们无法移植到更新版本的 ASP.NET，因此（虽然我们仍然需要它们）它们必须在当前版本上运行。显然，我们在让它们与现代浏览器一起工作时遇到了问题。我一直在 machine.config 文件中使用浏览器上限声明来修复其中一些问题。几个版本之前，Firefox 更改了其用户代理字符串，浏览器上限部分不再正确检测浏览器。所以现在当然什么都行不通了。唯一的解决办法，当然是让每个人都使用IE……显然这不是一个理想的情况。如果必须的话，我们可以继续以这种方式进行，但我很好奇是否有人遇到过类似的情况以及他们如何解决它（不进行某种升级）。我特别好奇是否有人通过修改浏览器 caps 文件解决了这个问题。我尝试对浏览器 caps 脚本进行临时修改，但收效甚微。如果有人好奇，您可以在这里找到更多信息： http://sling Five.com/pages/code/browserCaps/。
谢谢
We have some old in house apps that were written with asp.net 1.1. For various reasons they cannot be ported over to a more current version of asp.net and so (while we still need them) they must run at their current version. Obviously we have had problems getting them to work with modern browsers. I had been using a browser caps declaration in the machine.config file to fix some of these problems. A few versions ago, Firefox altered their user agent string and the browser caps section no longer detects the browser correctly. So now nothing works right of course. The only solution, make everyone use IE of course... Obviously this is not an ideal situation. We can continue on in this manner if we have to but I was curious if anyone had run into a similar situation and how they solved it (short of doing some sort of upgrade). I would be especially curious if anyone had solved this by modifying the browser caps file. I have tried to make adhoc modifications to the browser caps script with little success. If anyone is curious you can find more info on it here:
http://slingfive.com/pages/code/browserCaps/.
Thanks
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
我也遇到过类似的问题，只不过当前的 ASP.NET 版本带有不受欢迎的浏览器。 ASP.NET 4.0 在 SeaMonkey 内呈现 AutoPostBack 控件时存在问题。
作为我们可以在服务器上修复它之前的短期修复，我们让用户更改浏览器发送用户代理的方式。在 Firefox 中，您可以下载插件来切换用户代理。
显然，如果您的应用程序受众是公众，这不是一个解决方案，但如果您的受众是内部应用程序的少数精选员工，这可能是一个可能的解决方法。
I had a similar problem, except it was a current ASP.NET version with an unpopular browser. ASP.NET 4.0 has issues rendering AutoPostBack controls inside of SeaMonkey.
As a short-term fix until we could fix it at the server, we had the user change the way their browser sends their user agent. In Firefox, you can download a plug-in to switch your user agent.
Obviously this is not a solution if your app audience is the public, but if your audience is a few select employees on an internal app, it may be a possible workaround.