Skip to main content

LevelBlue Completes Acquisition of Cybereason.  Learn More

LevelBlue Completes Acquisition of Cybereason.  Learn More

Services
Cyber Advisory
Managed Cloud Security
Data Security
Managed Detection & Response
Email Security
Managed Network Infrastructure Security
Exposure Management
Security Operations Platforms
Incident Readiness & Response
SpiderLabs Threat Intelligence
Solutions
BY TOPIC
Offensive Security
Solutions to maximize your security ROI
Operational Technology
End-to-end OT security
Microsoft Security
Unlock the full power of Microsoft Security
Securing the IoT Landscape
Test, monitor and secure network objects
Why LevelBlue
About Us
Awards and Accolades
LevelBlue SpiderLabs
LevelBlue Security Operations Platforms
Security Colony
Partners
Microsoft Security
Unlock the full power of Microsoft Security
Technology Alliance Partners
Key alliances who align and support our ecosystem of security offerings
Loading...
Loading...

HOWTO: Controlling Caching of HTTPS content

Expand / Collapse


This article applies to:

  • WebMarshal 7.5.5 and above
  • Proxy caching

Question:

  • How do I control caching of HTTPS content?

Background:

WebMarshal 7.5.5 and above caches static files delivered over HTTPS by default.
  • This is a change from earlier versions that did not cache HTTPS content. This change reflects the reality that most reputable websites now use HTTPS for most content.
  • Static files generally include scripts, images, and other helper files that do not contain sensitive content.
  • HTTPS caching is only active for inspected HTTPS content. If your policy excludes a site from inspection, the content from the site will not be cached.

Procedure

To disable caching of HTTPS content:

  1. Add the following entry to the WebMarshal Proxy Configuration file (WMProxy.config.xml) on each processing server
  2. <WebMarshal>
    <Proxy>
    <Config>

    <Cache allowHTTPSCaching="false" />
    </Config>
    </Proxy>
    </WebMarshal>
  3. Restart the WebMarshal Proxy service.

Note

  • WMProxy.config.xml will include other entries. Do not change the other entries.
  • The Cache element may exist and contain other attributes. Add the new attribute to the existing element.
  • XML files are case sensitive.
  • For general information about editing XML settings files, see article Q12705.

To contact Trustwave about this article or to request support:


Rate this Article:
     

Add Your Comments


Comment submission is disabled for anonymous users.
Please send feedback to Trustwave Technical Support or the Webmaster
.