为什么COM的ScriptResource.axd pressed，即使IIS COM pression被禁用？ [英] Why is ScriptResource.axd compressed, even though IIS compression is disabled?

问题描述

我运行在IIS 6.0上的ASP.NET应用程序。通常我都COM pression开启动态和静态文件。不过，我转身COM pression暂时关闭，但的ScriptResource.axd仍发送COM pressed。这并不觉得自己是一个错误配置，为WebResource.axd的是不是COM pressed。

I run an ASP.NET application on IIS 6.0. Usually I have compression turned on for both dynamic and static files. However, I've turned compression off temporarily, but "ScriptResource.axd" is still sent compressed. This does not feel like a misconfiguration, as "WebResource.axd" is not compressed.

是什么ScriptResource和WebResource之间的差异，例如，前者是静止的COM pressed？它是如何让COM pressed？

What is the difference between ScriptResource and WebResource, such that the former is still compressed? How is it getting compressed?

感谢。

推荐答案

网络资源被的 AssemblyResourceLoader 类，其目的是获取装配资源并将它们用于在Web浏览器。网络资源的不的COM $ P $默认pssed。

Web Resources are handled by the AssemblyResourceLoader class, which is designed to retrieve assembly resources and serve them to the Web browser. Web Resources are not compressed by default.

脚本资源由 ScriptResourceHandler 类，这需要那些通过ScriptManager类引用的嵌入式脚本文件的所有请求照顾。
脚本资源的是的自动COM pressed用gzip默认情况下，HTTP传递。

Script Resources are handled by the ScriptResourceHandler class, which takes care of all requests for embedded script files that are referenced through the ScriptManager class. Script Resources are automatically compressed with GZIP by default for HTTP delivery.

这篇关于为什么COM的ScriptResource.axd pressed，即使IIS COM pression被禁用？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！