Bypass Reblaze for loadtesting or other purposes

Sometimes an admin needs to bypass Reblaze's traffic filtering, for example when "attacking" an application or server as part of a loadtest. Under normal circumstances, Reblaze would prevent this, because it would enforce rate limits and block the excessive requests from reaching the backend.

Specific requests can be exempted from Reblaze's traffic filtering (including rate limiting) by:

  • Creating a Global Filter with narrowly-defined Rules (which will only match those specific requests, and no others)

  • Selecting the Global Filter's Action to be one of type Skip

  • And ideally, defining a unique tag to assign to those requests, so they will be identifiable in the traffic logs.

Incoming requests that meet the criteria for the Global Filter will not subjected to filtering. They will be passed directly through to the backend.

Last updated