BUG: Script Errors with Cache-Control:no-cache HTTP Header and HTTP Compression
This article was previously published under Q327286
This article has been archived. It is offered "as is" and will no longer be updated.
If you read Web pages from a site, an HTML page may be incomplete, or you may receive script error messages such as the following in Microsoft Internet Explorer (Programming) version 6.0:
Object doesn't support this property or method
'(object reference)' is null or not an objectIt is also possible that an HTML page may be incomplete.
This occurs when you read Web pages from a site that uses all the following:
- Script in external files, for example, JScript (.js) files
- Frames and script inside the frames that refers to variables or to methods that are defined in other frames
- HTTP compression to compress the HTML and the script files
- HTTP headers that prevent the browser from caching the pages
The symptoms of this problem typically occur inconsistently and may appear random. Sometimes the error messages may appear when you first load the site. At other times the error messages may appear when you refresh the page.
To work around this problem, you can do either of the following:
- If you use a Cache-Control: no-cache HTTP header to prevent the files from caching, remove that header. In some situations, if you substitute an Expires HTTP header, you do not trigger the problem.
- Do not enable HTTP compression for the script files.
For additional information, click the article numbers below to view the articles in the Microsoft Knowledge Base:
234067 HOWTO: Prevent Caching in Internet Explorer
255801 How to Determine if HTTP Compression Is in UseFor more information about developing Web-based solutions for Microsoft Internet Explorer, visit the following Microsoft Web sites:
prevent caching gzip compressed error jscript vbscript
Article ID: 327286 - Last Review: 12/07/2015 12:09:20 - Revision: 6.2
Microsoft Internet Explorer 6.0
- kbnosurvey kbarchive kbbug kbpending KB327286