Static files such as iis html, CSS, Script, and images are not updated.

Files have been updated to the site, but client access is still not updated, mainly for various static files.
The gateway proxy server has a high possibility of caching. Check the reason first.
The proxy server cache also has some other performance. You can see the update effect during local access. The update effect can also be seen if the LAN access of the same network segment and Internet Explorer does not go through the proxy; the client directly uses a url to access static files (html pages, css files, scripts, etc.). The obtained files are not updated. The client updates the file name on the server and uses the new file name to access the files, the updated file can be obtained.

Tag Name	Example (s)	Description
Author	<Meta name = "AUTHOR" CONTENT = "Tex Texin">	The author's name.
Cache-control	<META HTTP-EQUIV = "CACHE-CONTROL" CONTENT = "NO-CACHE">	HTTP 1.1. Allowed values = PUBLIC | PRIVATE | NO-CACHE | NO-STORE. Public-may be cached in public shared caches Private-may only be cached in private cache No-Cache-may not be cached No-Store-may be cached but not archived The directive CACHE-CONTROL: NO-CACHE indicates cached information shocould not be Used and instead requests shocould be forwarded to the origin server. This directive Has the same semantics asPRAGMA: NO-CACHE. Clients shoshould include both PRAGMA: NO-CACHE and CACHE-CONTROL: NO-CACHE when a no-cache Request is sent to a server not known to be HTTP/1.1 compliant. Also see EXPIRES. Note:It may be better to specify cache commands in HTTP than in META statements, Where they can influence more than the browser, but proxies and other intermediaries That may cache information.
Content-Language	<META HTTP-EQUIV = "CONTENT-LANGUAGE" CONTENT = "en-US, fr">	Declares the primary natural language (s) of the document. May be used by search Engines to categorize by language.
CONTENT-TYPE	<META HTTP-EQUIV = "CONTENT-TYPE" CONTENT = "text/html; charsets = UTF-8">	The HTTP content type may be extended to give the character set. It is recommended To always use this tag and to specify the charset.
Copyright	<Meta name = "COPYRIGHT" CONTENT = "& copy; 2004 Tex Texin">	A copyright statement.
DESCRIPTION	<Meta name = "DESCRIPTION" CONTENT = "... summary of web page...">	The text can be used when printing a summary of the document. The text shocould not Contain any formatting information. Used by some search engines to describe your Document. Particle ly important if your document has very little text, is a frameset, Or has extensive scripts at the top.
EXPIRES	<META HTTP-EQUIV = "EXPIRES" CONTENT = "Mon, 22 Jul 2002 11:12:01 GMT">	The date and time after which the document shoshould be considered expired. An illegal EXPIRES date, e.g. "0", is interpreted as "now". Setting EXPIRES to 0 may thus be Used to force a modification check at each visit. Web robots may delete expired documents from a search engine, or schedule a revisit. HTTP 1.1 (RFC 2068) specifies that all HTTP date/time stamps MUST be generated in Greenwich Mean Time (GMT) and in RFC 1123 format. RFC 1123 format =Wkday "," SP date SP time SP "GMT" Wkday = (Mon, Tue, Wed, Thu, Fri, Sat, Sun) Date = 2 digit sp month SP 4 DIGIT; day month year (e.g., 02 Jun 1982) Time = 2 DIGIT ":" 2 DIGIT ":" 2 DIGIT; 00:00:00-23:59:59 Month = (Jan, Feb, Mar, Apr, May, Jun, Jul, Aug, Sep, Oct, Nov, Dec)
Keywords	<Meta name = "KEYWORDS" CONTENT = "sex, drugs, rock & roll">	The keywords are used by some search engines to index your document in addition To words from the title and document body. Typically used for synonyms and alternates Of title words. Consider adding frequent misspellings. e.g. heirarchy, hierarchy.
Pragma no-CACHE	<META HTTP-EQUIV = "PRAGMA" CONTENT = "NO-CACHE">	This directive indicates cached information shoshould not be used and instead requests Shocould be forwarded to the origin server. This directive has the same semantics As the CACHE-CONTROL: NO-CACHE directive and is provided For backwards compatibility with HTTP/1.0. Clients shoshould include both PRAGMA: NO-CACHE and CACHE-CONTROL: NO-CACHE when a no-cache Request is sent to a server not known to be HTTP/1.1 compliant. HTTP/1.1 clients shocould NOT send the PRAGMA request-header. HTTP/1.1 caches shold Treat "PRAGMA: NO-CACHE" as if the client had sent "CACHE-CONTROL: NO-CACHE ". Also see EXPIRES.
Refresh	<META HTTP-EQUIV = "REFRESH" CONTENT = "15; URL = http://www.I18nGuy.com/index.html">	Specifies a delay in seconds before the browser automatically reloads the document. Optionally, specifies an alternative URL to load, making this command useful RedirectingBrowsers to other pages.
ROBOTS	<Meta name = "ROBOTS" CONTENT = "ALL"> <Meta name = "ROBOTS" CONTENT = "INDEX, NOFOLLOW"> <Meta name = "ROBOTS" CONTENT = "NOINDEX, FOLLOW"> <Meta name = "ROBOTS" CONTENT = "NONE">	CONTENT = "ALL | NONE | NOINDEX | INDEX | NOFOLLOW | FOLLOW | NOARCHIVE" Default = empty = "ALL" "NONE" = "NOINDEX, NOFOLLOW" The CONTENT field is a comma separated list: INDEX: search engine robots shocould include this page. FOLLOW: robots shocould follow links from this page to other pages. NOINDEX: links can be pinned ed, although the page is not indexed. NOFOLLOW: the page can be indexed, but no links are stored ed. NONE: robots can ignore the page. NOARCHIVE: Google uses this to prevent archiving Of the page. See http://www.google.com/bot.html
GOOGLEBOT	<Meta name = "GOOGLEBOT" CONTENT = "NOARCHIVE">	In addition to the robots meta Command above, Google supports A GOOGLEBOT command. With it, you can tell Google that you do not want the page Archived, but allow other search engines to do so. If you specify this command, Google will not save the page and the page will be unavailable via its cache. SeeGoogle's FAQ.