HTTP/1.1 is far from dead: legacy SDKs, embedded devices, and many corporate proxies still negotiate it by default. The h11TrafficOnlyFilter lets you carve out that slice of traffic so you can apply targeted actions without touching modern HTTP/2 or HTTP/3 sessions, which is invaluable when you are debugging protocol specific behavior or planning a deprecation.
Reach for h11TrafficOnlyFilter when you need to scope rules to exchanges that were negotiated over HTTP/1.1, leaving HTTP/2 and HTTP/3 traffic untouched. The filter is evaluated as soon as Fluxzy has parsed the request headers from the client, so it pairs well with actions that modify headers, throttle bandwidth, or change the upstream behavior.
Common situations include:
Apply a bandwidth cap to legacy HTTP/1.1 traffic while leaving HTTP/2 clients on full speed. Useful for confirming a slow third party integration is not blocking modern users.
rules:
- filter:
typeKind: H11TrafficOnlyFilter
actions:
- typeKind: AverageThrottleAction
bandwidthBytesPerSeconds: 32768
Attach a tag so you can quickly filter the captured session view down to legacy traffic when reviewing the trace.
rules:
- filter:
typeKind: H11TrafficOnlyFilter
actions:
- typeKind: ApplyTagAction
tag:
value: legacy-http1
During a migration audit, return a clear error to any caller that still negotiates HTTP/1.1 against a specific host.
rules:
- filter:
typeKind: FilterCollection
operation: And
children:
- typeKind: H11TrafficOnlyFilter
- typeKind: HostFilter
pattern: api.example.com
operation: Exact
actions:
- typeKind: RejectWithStatusCodeAction
statusCode: 426
Select HTTP/1.1 exchanges only.
Evaluation scope defines the timing where this filter will be applied.
requestHeaderReceivedFromClient This scope occurs the moment fluxzy parsed the request header receiveid from client
h11TrafficOnlyFilter
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 |
The following examples apply a comment to the filtered exchange
Select HTTP/1.1 exchanges only.
rules:
- filter:
typeKind: H11TrafficOnlyFilter
actions:
- typeKind: ApplyCommentAction
comment: filter was applied
View definition of H11TrafficOnlyFilter for .NET integration.
The following filters are related to this filter:
Fluxzy uses the parsed request line and connection state, so it reflects the protocol that was actually used for the exchange, not just what the client advertised.
Yes. Use separate rule blocks, one per filter, so each protocol path gets its own actions. They do not interfere with each other.
WebSocket upgrades initiated over HTTP/1.1 are matched because the underlying exchange uses HTTP/1.1. Use isWebSocketFilter alongside it if you want only WebSocket traffic.