deleteFilter Filter

Select exchanges whose HTTP method is DELETE, useful for protecting destructive endpoints or auditing teardown traffic during a capture.

deleteFilter is a verb specific shortcut around methodFilter. It makes rule files self documenting when the intent is to act on destructive requests, which is one of the most common reasons engineers reach for a method filter in the first place.

When to use this filter

Use deleteFilter when you want a rule to apply specifically to HTTP DELETE requests. DELETE is the method clients use for destructive operations, so it often deserves special treatment such as confirmation, blocking on a staging environment, or extra logging.

Typical situations:

Rejecting DELETE requests to a production host while a release is in progress.
Tagging every DELETE so a session report can highlight teardown operations.
Verifying that an automated test correctly emits DELETE calls in its cleanup phase.

The filter fires on the requestHeaderReceivedFromClient scope. It is equivalent to methodFilter configured for DELETE, but reads more clearly in rule files that focus on REST verbs.

Real world examples

Block DELETE on a production host during a freeze

Reject every DELETE request targeted at the production API while a deploy freeze is in effect, to prevent accidental cleanups.

rules:
- filter:
    typeKind: FilterCollection
    operation: and
    children:
    - typeKind: HostFilter
      pattern: api.example.com
      operation: Exact
    - typeKind: DeleteFilter
  actions:
  - typeKind: RejectWithStatusCodeAction
    statusCode: 403

Audit DELETE calls during a load test

Tag every DELETE in the capture so the post run report can count teardown operations and verify the test exercised the full lifecycle.

rules:
- filter:
    typeKind: DeleteFilter
  actions:
  - typeKind: ApplyTagAction
    tag:
      value: lifecycle-teardown

Confirm an automated cleanup actually deletes the right resources

Append every DELETE request line to a file so you can later diff it against the expected cleanup plan.

rules:
- filter:
    typeKind: DeleteFilter
  actions:
  - typeKind: FileAppendAction
    filename: /tmp/fluxzy-deletes.log
    text: "{request:url}\n"

Reference

deleteFilter

Description

Select exchanges with DELETE method

Evaluation scope

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

YAML configuration name

deleteFilter

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

The following examples apply a comment to the filtered exchange

Select exchanges with DELETE method.

rules:
- filter:
    typeKind: DeleteFilter
  actions:
  - typeKind: ApplyCommentAction
    comment: filter was applied

.NET reference

View definition of DeleteFilter for .NET integration.

Frequently asked questions

What is the difference between deleteFilter and methodFilter?

deleteFilter is a shorthand for methodFilter with method set to DELETE. The behavior is identical, deleteFilter is just easier to read in YAML.

Does it match DELETE on any host?

Yes, on its own deleteFilter matches every DELETE regardless of destination. Combine it with hostFilter or authorityFilter to scope by target.

Can I invert the filter?

Yes. Set inverted: true to select every exchange that is not a DELETE. That is useful when you want to apply a rule to safe methods only.

Does it cover the WebDAV DELETE method?

Yes. The filter matches on the literal DELETE method token, which is the same for HTTP and WebDAV.

Learn more about Fluxzy rules

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

Browse all directives