Stripping request headers is one of the most frequent rewrites engineers need from a debugging proxy. deleteRequestHeaderAction does exactly that, with no surprises around duplicate headers or case sensitivity. Pair it with a precise filter so you only mutate the traffic you actually want to change.
Use deleteRequestHeaderAction whenever you need an outbound request to leave Fluxzy without a header that the client originally sent. The action removes every instance of the named header, so duplicates are handled in one rule.
Typical situations include:
Authorization header is missing.Cookie to test anonymous behaviour against an authenticated client.X-Request-Id, Traceparent) before they leave your network.The action runs on the requestHeaderReceivedFromClient scope. Header name matching is case insensitive, which matches the HTTP specification.
Lets you exercise the anonymous code path without changing the calling client.
rules:
- filter:
typeKind: HostFilter
pattern: api.internal.example.com
actions:
- typeKind: DeleteRequestHeaderAction
headerName: Authorization
Useful when a third party rejects requests carrying your internal trace identifiers.
rules:
- filter:
typeKind: PathFilter
pattern: /v1/webhooks
actions:
- typeKind: DeleteRequestHeaderAction
headerName: X-Internal-Trace-Id
A quick way to flush session state at the wire level without touching the client cookie jar.
rules:
- filter:
typeKind: HostFilter
pattern: legacy.example.com
actions:
- typeKind: DeleteRequestHeaderAction
headerName: Cookie
Remove request headers. This action removes every occurrence of the header from the request.
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
deleteRequestHeaderAction
The following table describes the customizable properties available for this action:
| Property | Type | Description | DefaultValue |
|---|---|---|---|
| headerName | string |
The following examples apply this action to any exchanges
Remove every Cookie header from request.
rules:
- filter:
typeKind: AnyFilter
actions:
- typeKind: DeleteRequestHeaderAction
headerName: Cookie
View definition of DeleteRequestHeaderAction for .NET integration.
The following actions are related to this action:
No. Every occurrence of the header is removed. Some clients legitimately repeat headers like Cookie, and this action takes them all out in a single pass.
updateRequestHeaderAction rewrites the value of an existing header. deleteRequestHeaderAction removes the header entirely.
No. HTTP header names are case insensitive, so Authorization, authorization, and AUTHORIZATION all match the same rule.
No. Pseudo headers belong to the HTTP/2 framing layer and cannot be removed at the application level. Use forceRemotePortAction or forwardAction if you need to change the destination.