blocks|key|4293668|text|您需要在IIS中为该扩展名创建MIME类型：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4293669|要为特定扩展名定义MIME类型，请执行以下步骤：|4293670|4293671|打开IIS+Microsoft管理控制台(MMC)，右键单击本地计算机名称，然后单击Properties.|ordered-list-item|4293672|Click+HTTP头。|4293673|单击MIME类型。|4293674|单击新建。|4293675|在扩展名框中，键入所需的文件扩展名(例如，.axed)|4293676|<>H111>在MIME类型框中，键入新设置。请注意，您必须重新启动万维网发布服务或等待辅助进程重新启动才能使更改生效。在此示例中，IIS现在提供扩展名为.axed的文件。|4293677|entityMap^0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|T|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|U|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|V|8|@]|9|@]|A|$]]|$1|E|3|F|5|G|7|W|8|@]|9|@]|A|$]]|$1|H|3|I|5|G|7|X|8|@]|9|@]|A|$]]|$1|J|3|K|5|G|7|Y|8|@]|9|@]|A|$]]|$1|L|3|M|5|G|7|Z|8|@]|9|@]|A|$]]|$1|N|3|O|5|G|7|10|8|@]|9|@]|A|$]]|$1|P|3|Q|5|6|7|11|8|@]|9|@]|A|$]]|$1|R|3|-4|5|6|7|12|8|@]|9|@]|A|$]]]|S|$]]

You need to create a MIME type for that extension in IIS:

To define a MIME type for a specific extension, follow these steps:

<ol>
<li>Open the IIS Microsoft Management Console (MMC), right-click the local computer name, and then click Properties.</li>
<li>Click HTTP Headers.</li>
<li>Click MIME Types.</li>
<li>Click New.</li>
<li>In the Extension box, type the file name extension that you want (for example, .axed)</li>
<li>In the MIME Type box, type application/octet-stream.</li>
<li>Apply the new settings. Note that you must restart the World Wide Web Publishing Service or wait for the worker process to recycle for the changes to take effect. In this example, IIS now serves files with the .axed extension.</li>
</ol>

blocks|key|1076586|text|不久前，我们的生产服务器上出现了错误500(不是404，但谁知道呢)。无法加载任何脚本资源。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1076587|问题在于我们的开发服务器和生产服务器之间的时间差。是-7个小时。.NET抛出异常，因为它试图使用具有嵌入脚本资源的程序集的“将来的时间”。|1076588|逐步减少{website}/bin/文件夹(实际上是其中的程序集)的创建日期解决了这个问题。|offset|length|style|CODE|1076589|entityMap^0|0|0|4|E|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|M|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|N|8|@$F|O|G|P|H|I]]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|K|$]]

We had error 500(it is not 404, but who knows) on our production server some time ago. No script resources were able to load.

The problem was in the time difference between our development and production servers. It was -7 hours. .NET threw an exception because of it tried to use a "time in the future" of an assembly with embedded script resources.

Decreasing <code>{website}/bin/</code> folder (actually assemblies' in it) creation date by day solved the problem.

blocks|key|101032|text|您是否可以发出一个失败的“坏”请求，然后检查服务器的系统和应用程序事件日志？|type|unstyled|depth|inlineStyleRanges|entityRanges|data|101033|围绕axd有几个问题可能导致404s或500s+(例如Alex提到的“未来时间”问题)，但它们会在事件日志中留下足迹。|101034|查看并发布任何提到axds的日志条目。|101035|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

Can you make a "bad" request that fails and then check the server's system and application event logs?

There are several issues around axd that can cause 404s or 500s (such as the "time in the future" issue mentioned by Alex), but they leave a footprint in the event log.

Have a look and post any log entries that mention axds.

blocks|key|101068|text|您可以检查以下内容：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|101069|101070|在IIS管理控制台中检查是否允许.axd扩展名(默认的HTTP处理程序扩展名)。|ordered-list-item|101071|还检查“验证文件是否存在”复选框是否为未选中的。如果在web.config中正确注册了extension.|101072|Check处理程序，则在选择axd之后单击“编辑”按钮后会出现此屏幕。根据IIS版本的不同，它也应该在正确的配置部分中。对于IIS6和IIS7经典模式，它应该是<system.web><httpHandlers>。对于IIS7集成模式，应在<system.webServer><handlers>.|offset|length|style|CODE|101073|中注册|101074|entityMap^0|0|0|0|0|28|Q|3C|S|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|S|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|T|8|@]|9|@]|A|$]]|$1|F|3|G|5|E|7|U|8|@]|9|@]|A|$]]|$1|H|3|I|5|E|7|V|8|@$J|W|K|X|L|M]|$J|Y|K|Z|L|M]]|9|@]|A|$]]|$1|N|3|O|5|6|7|10|8|@]|9|@]|A|$]]|$1|P|3|-4|5|6|7|11|8|@]|9|@]|A|$]]]|Q|$]]

You can check the following:

<ol>
<li>Check in the IIS management console that the .axd extension (the default HTTP handler extension) is allowed.</li>
<li>Also check if the “Verify if file exists” checkbox is unchecked. This screen appears after you click the "Edit" button after selecting the axd extension.</li>
<li>Check if the HTTP handler is correctly registered in web.config. It should also be in the right config section depending on the IIS version. For IIS6 and IIS7 Classic mode it should be in <code>&lt;system.web&gt;&lt;httpHandlers&gt;</code>. For IIS7 Integrated mode it should be registered in <code>&lt;system.webServer&gt;&lt;handlers&gt;</code>.</li>
</ol>

blocks|key|102124|text|如果您使用的是IIS7，请确保将处理程序添加到<system.webServer><handlers>部分：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|102125|<add+name="MyName"+path="MyName.axd"+verb="*"+type="NameSpace.Class,+Assembly"+/>|code-block|syntax|javascript|102126|entityMap^0|N|S|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@$9|N|A|O|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|P|8|@]|D|@]|E|$I|J]]|$1|K|3|-4|5|6|7|Q|8|@]|D|@]|E|$]]]|L|$]]

if you're on IIS7 make sure you add the handler to the <code>&lt;system.webServer&gt;&lt;handlers&gt;</code> section:

<pre><code>&lt;add name="MyName" path="MyName.axd" verb="*" type="NameSpace.Class, Assembly" /&gt;
</code></pre>

blocks|key|102141|text|确认在Request+Filtering中，您可以*将.axd作为允许的扩展名，或者*在编辑请求过滤设置中勾选Allow+unlisted+file+name+extensions|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|102142|下面的web.config部分也可以达到同样的效果：|102143|<system.webServer>
++++<security>
++++++++<requestFiltering>
++++++++++++<fileExtensions>
++++++++++++++++<add+fileExtension=".axd"+allowed="true"+/>
++++++++++++</fileExtensions>
++++++++</requestFiltering>
++++</security>
</system.webServer>|code-block|syntax|javascript|102144|entityMap^0|3|H|R|4|1J|Z|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@$9|P|A|Q|B|C]|$9|R|A|S|B|C]|$9|T|A|U|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|V|8|@]|D|@]|E|$]]|$1|H|3|I|5|J|7|W|8|@]|D|@]|E|$K|L]]|$1|M|3|-4|5|6|7|X|8|@]|D|@]|E|$]]]|N|$]]

Confirm that in <code>Request Filtering</code> you either
 * have <code>.axd</code> as an Allowed extension, or
 * have <code>Allow unlisted file name extensions</code> ticked in Edit Request Filtering Settings

The same effect can be achieved with the following web.config section:

<pre><code>&lt;system.webServer&gt;
 &lt;security&gt;
 &lt;requestFiltering&gt;
 &lt;fileExtensions&gt;
 &lt;add fileExtension=".axd" allowed="true" /&gt;
 &lt;/fileExtensions&gt;
 &lt;/requestFiltering&gt;
 &lt;/security&gt;
&lt;/system.webServer&gt;
</code></pre>

blocks|key|4293989|text|在我的例子中，我使用自动转换从.NET+2.0转移项目。Converter添加了<system.webServer>部分以及<system.web>中的所有处理程序和模块。但是，它为每个处理程序添加了以下属性：preCondition="integratedMode，runtimeVersionv2.0"一旦我删除了该属性，404就停止了，处理程序开始工作。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|BOLD|entityRanges|data|4293990|entityMap^0|14|I|1Q|C|2X|1C|0^^$0|@$1|2|3|4|5|6|7|I|8|@$9|J|A|K|B|C]|$9|L|A|M|B|C]|$9|N|A|O|B|D]]|E|@]|F|$]]|$1|G|3|-4|5|6|7|P|8|@]|E|@]|F|$]]]|H|$]]

In my case, I was transferring project from .NET 2.0 using automatic conversion. Converter added the <code>&lt;system.webServer&gt;</code> section and all the handlers and modules that are in the <code>&lt;system.web&gt;</code>. However, for each handler it added the following attribute: preCondition="integratedMode,runtimeVersionv2.0"
Once I removed the attribute the 404s stopped and handler started to work.

blocks|key|102190|text|我在模块中添加了一个属性runAllManagedModulesForAllRequests="true"。节点的system.webServer部分，404s停止，处理程序开始工作。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|102191|entityMap^0|2|2|C|15|1L|G|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]|$9|K|A|L|B|C]|$9|M|A|N|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|O|8|@]|D|@]|E|$]]]|G|$]]

I added a attribute runAllManagedModulesForAllRequests="true" into modules.. node of the system.webServer section, the 404s stopped and handler started to work.

blocks|key|102202|text|如果这对任何人有帮助的话，我也有同样的问题，我们几乎没有花2天的时间。在3台服务器上，一切正常，但在这台服务器上，404不会停止。解决方案是，我将poold从集成更改为经典，这很有效|type|unstyled|depth|inlineStyleRanges|entityRanges|data|102203|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

If this will help anyone, I had the same problem, few of us spent 2 days on. On 3 servers everything worked ok and allso on development but on this server 404 non stop. The solution, I changed poold from integrated to classic and that worked

Why do all of my .axd files generate a 404 error when on our production server?

.axd files generate a 404 error

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

为什么我的所有.axd文件在我们的生产服务器上都会生成404错误？

问.axd文件生成404错误
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问.axd文件生成404错误EN