ASP.NET ScriptManager 在 Chrome 中引起警告

发布于 2024-07-15 07:40:03 字数 940 浏览 8 评论 0 原文

我在 chrome 开发人员 javascript 控制台中收到以下警告：

未捕获的语法错误：意外的标记 < http://.../Question.asmx/js（第 1 行）

资源被解释为脚本，但是使用 MIME 类型 text/html 传输。 http://.../Question.asmx/js

HTML 源代码看起来不错：

<script src="../../../Question.asmx/js" type="text/javascript"></script>

我使用 ASP ScriptManager 来包含这些 Web 服务。它们工作得很好，我只是想知道问题到底是什么，因为我有强迫症问题，所以如何摆脱警告。

编辑：不涉及任何自定义处理程序。它只是我使用脚本管理器包含的一个标准 WebService：

<asp:ScriptManager runat="server" ID="scm1" EnablePageMethods="true" EnablePartialRendering="true" >
        <Services>
            <asp:ServiceReference Path="~/Question.asmx" />
        </Services>
    </asp:ScriptManager>

原文

I get the following warning in chrome developer javascript console:

Uncaught SyntaxError: Unexpected token
< http://.../Question.asmx/js (line 1)

Resource interpreted as script but
transferred with MIME type text/html.
http://.../Question.asmx/js

The HTML source code looks fine:

<script src="../../../Question.asmx/js" type="text/javascript"></script>

I use ASP ScriptManager to include those web services. They work fine, I was just wondering what exactly the problem is and, because I have an OCD problem, how to get rid of the warnings.

EDIT:
There is no custom handler involved. It's just a standard WebService that I include by using the scriptmanager:

<asp:ScriptManager runat="server" ID="scm1" EnablePageMethods="true" EnablePartialRendering="true" >
        <Services>
            <asp:ServiceReference Path="~/Question.asmx" />
        </Services>
    </asp:ScriptManager>

分享到QQ

分享到微博

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

发布评论

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

方觉久 2024-07-22 07:40:03

第二个警告是因为您的自定义处理程序 (Question.asmx) 未正确设置要发回的资源的 MIME 类型。

您应该将以下内容添加到 ProcessRequest 方法中：

context.Response.ContentType = "text/javascript";

这也可能会消除第一个错误，因为 HTML 页面应该以

The second warning is because your custom handler (Question.asmx) is not setting the mime type of the resource you're sending back correctly.

You should add the following to the ProcessRequest method:

context.Response.ContentType = "text/javascript";

That will probably also get rid of the first error, as an HTML page should start with a <!Doctype element to be valid, which is what I believe that error is complaining about.

回复收藏 0 原文