The most widely used solution to force servers and browsers to not cache files is to provide a unique parameter along with the request for the file.
For example, instead of requesting "Style.css", the request would become "Style.css?rnd=12345"
A work-around solution is to use an IncludeHTMLFile element instead. The IncludeHTMLFile element allows a developer to utilize any valid HTML, including the <link> and <script> tags. This provides the ability to append a version number, random GUID or SessionID to the end of the request, and apply that information to the HEAD of generated HTML.
For example, to only cache a stylesheet for a user's session:
<link rel="stylesheet" href="./_SupportFiles/Style.css?rnd=@Function.SessionID~">
To never cache a stylesheet for any user:
<link rel="stylesheet" href="./_SupportFiles/Style.css?rnd=@Function.GUID~">
A developer could even control the file caching based on a product release number stored as a constant.
<link rel="stylesheet" href="./_SupportFiles/Style.css?rnd=@Constant.VersionID~">
An example to control the caching of a script file based on a user's session:
Subsequent Session Reload: