anyFilter Filter

Selects every exchange that flows through Fluxzy, useful as a catch all entry in a rule file or as a placeholder during development.

anyFilter is the simplest filter in Fluxzy and a useful primitive for global behavior. Place it at the top of a rule file when you want a default action that applies before more specific filters kick in.

When to use this filter

Use anyFilter whenever you want an action to apply to every exchange without restriction. It is the proxy equivalent of a wildcard match. Common use cases include:

Applying a global header, tag or logging action across the entire capture.
Setting up scaffolding while you write more specific filters, you start with anyFilter and tighten the match later.
Defining a default outbound certificate or upstream proxy that should be used everywhere.

Because the filter evaluates on the onAuthorityReceived scope, anyFilter rules trigger as soon as Fluxzy learns the destination authority, so they apply to both CONNECT tunnels and direct HTTP traffic. Combine it with inverted: true only sparingly, an inverted anyFilter matches nothing and is rarely what you want.

Real world examples

Add an investigation tag to every exchange

Mark every captured exchange with a session tag so you can correlate the trace with an external incident identifier later.

rules:
- filter:
    typeKind: AnyFilter
  actions:
  - typeKind: ApplyTagAction
    tag:
      value: incident-4821

Apply a default upstream proxy to all traffic

Route every Fluxzy outbound connection through a corporate egress proxy unless a more specific rule overrides this default.

rules:
- filter:
    typeKind: AnyFilter
  actions:
  - typeKind: UpStreamProxyAction
    host: egress.corp.example.com
    port: 8080

Inject a debugging header on every request

Add a tracing header on every outbound request so the upstream service knows the traffic comes from your Fluxzy session.

rules:
- filter:
    typeKind: AnyFilter
  actions:
  - typeKind: AddRequestHeaderAction
    headerName: X-Debug-Source
    headerValue: fluxzy-session

Reference

anyFilter

Description

Select all exchanges

Evaluation scope

Evaluation scope defines the timing where this filter will be applied.

onAuthorityReceived This scope denotes the moment fluxzy is aware the destination authority. In a regular proxy connection, it will occur the moment where fluxzy parsed the CONNECT request.

YAML configuration name

anyFilter

Settings

This filter has no specific characteristic

The following table describes the customizable properties available for this filter:

Property	Type	Description	DefaultValue
inverted	boolean	Negate the filter result	false

Example of usage

This filter has no specific usage example

.NET reference

View definition of AnyFilter for .NET integration.

Frequently asked questions

Does anyFilter affect performance?

No noticeable cost. The filter does no comparison and resolves to true immediately, so it is cheaper than any pattern based filter.

Why would I ever invert anyFilter?

You normally would not. An inverted anyFilter never matches, so it is useful only to temporarily disable a rule while keeping its YAML in place.

Will anyFilter match WebSocket and gRPC exchanges?

Yes. anyFilter does not look at the protocol, so it covers HTTP/1.1, HTTP/2, WebSocket upgrades and gRPC streams equally.

Can multiple rules with anyFilter coexist?

Yes. Each rule is independent. All matching rules apply in declaration order, which is convenient for stacking global actions.

Learn more about Fluxzy rules

Rule file syntax reference Importing YAML rules into Fluxzy Desktop Using rule files with Fluxzy CLI

Browse all directives