当前位置：文江博客话题详情

JQuery 到 asmx 在 Windows 2008 R2 SP1 上失败

发布于 2024-10-26 15:29:59 字数 1552 浏览 6 评论 0原文

自从安装 SP1 以来，我们在从 JQuery 客户端代码调用 asmx 页面时遇到了问题。

IIS 将 JQuery post 调用指向他的默认 404 页面。

我们对环境进行了角色恢复，断言此问题是由 SP1 引起的，并且测试证实了这一点。

等待修复@MS

使用的技术：

ASP.Net 4.0 - jQuery - IIS 7.5 - Windows 2008 R2 SP1

--Bart

代码示例调用（前端）：

  // Code to load vars...
  $.ajax({

              type: "POST",
              url: "/Handlers/ProductRating.asmx/RateProduct",
              data: "{'uniqueId':'" + uniqueId + "','productId':'" + productId + "','points':" + points.toString() + ",'showOwnScore':" + showOwnScore.toString() + "}",
              contentType: "application/json; charset=utf-8",
              dataType: "json",
              success: function(response) {
                   alert('success');
              },
              failure: function(msg) {
                alert('something went wrong');
              }
            });
        }

代码后端：

 [ScriptService]
public class ProductRating : System.Web.Services.WebService
{

    [WebMethod(EnableSession=true)]
    public RateProductResponse RateProduct(Guid uniqueId, Guid productId, int points, bool showOwnScore)
    {
       //Implementation
    }

快照1：使用 SP1： http://img812.imageshack.us/i/capture2r.png/

快照2：没有 SP1： http://img190.imageshack.us/i/capture1qx.png/

原文

Since the installation of SP1 we are facing problems in calling asmx pages from JQuery client code.

IIS is pointing the JQuery post call to his default 404 page.

We did a roleback of our environment to assert this issue is caused by SP1 and tests confirm it.

Waiting for a fix @MS

Technologies used:

ASP.Net 4.0 -
JQuery -
IIS 7.5 -
Windows 2008 R2 SP1

--Bart

Code Sample calling (front-end):

  // Code to load vars...
  $.ajax({

              type: "POST",
              url: "/Handlers/ProductRating.asmx/RateProduct",
              data: "{'uniqueId':'" + uniqueId + "','productId':'" + productId + "','points':" + points.toString() + ",'showOwnScore':" + showOwnScore.toString() + "}",
              contentType: "application/json; charset=utf-8",
              dataType: "json",
              success: function(response) {
                   alert('success');
              },
              failure: function(msg) {
                alert('something went wrong');
              }
            });
        }

Code back-end:

 [ScriptService]
public class ProductRating : System.Web.Services.WebService
{

    [WebMethod(EnableSession=true)]
    public RateProductResponse RateProduct(Guid uniqueId, Guid productId, int points, bool showOwnScore)
    {
       //Implementation
    }

Snapshot1 : With SP1:
http://img812.imageshack.us/i/capture2r.png/

Snapshot2 : Without SP1:
http://img190.imageshack.us/i/capture1qx.png/

分享到QQ

分享到微博

如果你对这篇内容有疑问，欢迎到本站社区发帖提问参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。

发布评论

需要登录才能够评论，你可以免费注册一个本站的账号。

格子衫的從容 2024-11-02 15:29:59

我可以通过在 web.config 中添加以下内容来实现此功能，

我看到另一个网站建议清除处理程序，但这使一切变得更糟。通过此更新，我能够再次调用我的网络服务。

<system.webServer>
    <handlers>
        <add name="AsmxRoutingHandler" verb="*" path="*.asmx"  type="System.Web.Script.Services.ScriptHandlerFactory, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" />
    </handlers>
</system.webServer>

I was able to get this working with the following addition to my web.config

I saw another site that suggested clearing the handlers, but that made everything way worse. With this update, I was able to call my web services once again.

<system.webServer>
    <handlers>
        <add name="AsmxRoutingHandler" verb="*" path="*.asmx"  type="System.Web.Script.Services.ScriptHandlerFactory, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" />
    </handlers>
</system.webServer>

回复收藏 0 原文

萌梦深 2024-11-02 15:29:59

我也有同样的问题。

创建包含以下行的 Web.Config 文件：

<?xml version="1.0" encoding="utf-8"?>
<configuration>
    <location path="." inheritInChildApplications="false">
        <system.web>
            <httpHandlers>
                <clear />
                <add verb="*" path="*.asmx" validate="false" type="System.Web.Script.Services.ScriptHandlerFactory, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" />
                <add path="*" verb="GET,HEAD,POST" type="System.Web.DefaultHttpHandler" validate="True" />
            </httpHandlers>
        </system.web>
    </location>
</configuration>

将其复制到提供受影响脚本的目录中，然后重新启动 Web 服务器。

这些行将覆盖您首选的 HttpHandler 并将其设置为使用默认处理程序。

祝你好运！

I had the same problem.

Create a Web.Config file containing the following lines:

<?xml version="1.0" encoding="utf-8"?>
<configuration>
    <location path="." inheritInChildApplications="false">
        <system.web>
            <httpHandlers>
                <clear />
                <add verb="*" path="*.asmx" validate="false" type="System.Web.Script.Services.ScriptHandlerFactory, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" />
                <add path="*" verb="GET,HEAD,POST" type="System.Web.DefaultHttpHandler" validate="True" />
            </httpHandlers>
        </system.web>
    </location>
</configuration>

Copy this into the directory(s) where you serve out your affected scripts, and restart your web server.

These lines will override your preferred HttpHandlers and set it to use the default handlers instead.

Good luck!

回复收藏 0 原文