|2003-11-15, 02:14 AM||#1|
在執行微軟Internet Information Services (IIS) 6.0的Windows Server 2003系統上，使用GNU zip（Gzip）進行壓縮的靜態文件可能會不可用或包含有來自Web伺服器中其他文件的內容。如果出現這種情況，返回客戶端的頁面將會產生出錯，而且還可能造成訪問衝突的現象。
FIX: IIS 6.0 Gzip Compression Corruption Causes Access Violations
On Microsoft Windows Server 2003 running Microsoft Internet Information Services (IIS) 6.0, static files that are compressed using gzip may become corrupted and may include content from other files on the Web server. If this behavior occurs, the page that is returned to the client is not rendered correctly. An access violation may also occur.
Note This problem can affect Outlook Web Access (OWA) users and may cause script errors to be returned in the OWA pages.
The following file is available for download from the Microsoft Download Center:
Download the 831464 package now.
For additional information about how to download Microsoft Support files, click the following article number to view the article in the Microsoft Knowledge Base:
119591 How to Obtain Microsoft Support Files from Online Services
Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help to prevent any unauthorized changes to the file.
No prerequisites are required.
You do not have to restart your computer after you apply this hotfix.
The English version of this hotfix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel. Date Time Version Size File name
29-Oct-2003 22:50 6.0.3790.99 336,384 W3core.dll
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.
You may be able to temporarily work around this problem by deleting the cached, compressed copy of the affected file or files on the IIS server. By default, the compressed file is located the following folder:
%windir%\IIS Temporary Compressed Files
This temporary directory location can be changed in IIS Manager on the Service tab in the Web Sites property sheet.