Link11 WAAP
v2.12
v2.12
  • Link11 WAAP v2.12 Portal
  • Introduction
  • Getting Started
  • Setup Checklists
  • Marketplace onboarding
  • Console UI Walkthrough
    • Traffic
      • Traffic Concepts
      • Dashboard
      • View Log
    • Security
      • Security Section Concepts
      • Static Rules
      • Dynamic Rules
      • Quarantined
      • Profiles
        • Profile Concepts
        • Profiles
        • ACL Policies
        • WAF/IPS Policies
        • Custom Signature
      • Args Analysis
    • Settings
      • Web Proxy
        • General Settings
        • Application Profiles
        • Security Profiles
      • SSL Management
      • DNS
      • Planet Overview
      • Account
  • Using the product
    • Best Practices
      • Saving and Publishing Your Changes
      • Enabling Passive Challenges
      • Using the Reblaze Query Box
      • Understanding and Diagnosing Traffic Issues
    • How Do I...
      • Ban, Unban, and Whitelist Traffic Sources
      • Bypass Rate Limits for Loadtesting
      • Control Caching Behavior
      • Filter by Content
      • Quickly Block an Attacker
      • Secure Traffic from a Third-Party Page
      • Set Rate Limits
      • Set up SIEM/SOC integration
      • Video Tutorials
        • DNS Training
        • SSL Training
    • API
      • Reblaze REST API
      • Mobile SDK
  • Reference Information
    • Access log-structure
    • Acronyms
    • Deployment Terminology
    • Hostile Bot Detection / RCSI
      • Environmental detection and browser verification
      • Client authentication
      • Biometric behavioral verification
    • HTTP Response Codes
    • Pattern Matching Syntax
    • Signatures
    • TTL Expression Syntax
  • Support
Powered by GitBook
On this page

Was this helpful?

Export as PDF
  1. Using the product
  2. How Do I...

Control Caching Behavior

as administered in Settings -> Web Proxy -> Application Profiles -> Cache Modes

PreviousBypass Rate Limits for LoadtestingNextFilter by Content

Last updated 5 years ago

Was this helpful?

Web clients can cache resources from a server. Afterwards, a client can access its local cache, which reduces the number of requests sent to the server.

Servers can instruct clients to implement caching in certain ways. Servers can also set separate caching policies for any intermediary proxies in-between the server and the client.

Reblaze is a proxy between the clients and the origin (the upstream server). When the origin responds to clients, the outgoing responses pass through Reblaze. You can instruct Reblaze to preserve or alter the caching instructions in those responses.

On the page, the Cache Operation Mode is where you define Reblaze's caching behavior. There are several aspects to this:

  • Whether Reblaze includes caching instructions in the response to the client.

  • If so, whether they are the instructions from the origin server, or if Reblaze should override them and send different instructions instead.

  • Whether Reblaze itself caches the response content.

Here are the Cache Operation Modes and their effects.

Cache Operation Mode

Are caching instructions sent to the client?

Are the instructions the same as the origin's?

Does Reblaze cache response content?

Comments

Honor Origin

Yes

Yes

Yes, if the origin says to do so.

Reblaze will comply with the origin, and pass along its caching instructions to the client.

Active Pipe

Yes

No

Complies with TTL settings

Reblaze will generate caching instructions for the client in accordance with the Client TTL and CDN TTL settings in the section, and will also comply with them itself.

Passive Pipe

Yes

No

No

Reblaze will generate caching instructions for the client in accordance with the Client TTL and CDN TTL settings in the section, but will not store anything itself.

Neutral Pipe

Yes

Yes

No

Reblaze will pass the origin's caching instructions to the client, without caching anything itself.

Reset Headers

No

n/a

No

Reblaze will remove all cache headers sent by the origin, and will send the response to the client without any cache directive.

No Cache

Yes

No

No

Reblaze will send no-cache instructions to the client: Cache-Control "max-age=0, no-cache, no-store" andPragma no-cache.

Private

Yes

No

Complies with TTL settings

Reblaze will generate caching instructions for the client in accordance with the Client TTL and CDN TTL settings in the section, and will also comply with them itself. In addition, the client's instructions will include Cache-Control private

Application Profiles
Application Profiles
Application Profiles
Application Profiles