postFilter is the dedicated selector for HTTP POST exchanges in a Fluxzy rule. It mirrors the other verb specific filters (getFilter, putFilter, deleteFilter, patchFilter) and keeps your YAML readable when you only care about write operations or form submissions. Pair it with any action below to act on the POST side of an API.
Reach for postFilter when a rule should only apply to POST requests. POST is the workhorse verb for form submissions, resource creation, and a wide range of RPC style endpoints. The filter is a convenience wrapper around methodFilter with the verb fixed to POST, which keeps the YAML compact.
Typical situations:
The filter evaluates on the requestHeaderReceivedFromClient scope, so the method is known as soon as the request line is parsed. Combine it with pathFilter, jsonRequestFilter or formRequestFilter for finer scoping.
Apply a tag to all POST requests so write operations stand out in the Fluxzy capture view when reviewing API traffic.
rules:
- filter:
typeKind: PostFilter
actions:
- typeKind: ApplyTagAction
tag:
value: post
Attach a bearer token only to POST requests heading to the API host, leaving GET requests untouched.
rules:
- filter:
typeKind: FilterCollection
children:
- typeKind: PostFilter
- typeKind: HostFilter
pattern: api.example.com
actions:
- typeKind: AddAuthorizationBearerAction
token: dev-token-123
Slow down every POST to /checkout to reproduce a customer report about timeouts on slow networks.
rules:
- filter:
typeKind: FilterCollection
children:
- typeKind: PostFilter
- typeKind: PathFilter
pattern: /checkout
operation: StartsWith
actions:
- typeKind: AverageThrottleAction
bandwidthBytesPerSeconds: 16384
Select POST (request method) only exchanges.
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
postFilter
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 POST (request method) only exchanges.
rules:
- filter:
typeKind: PostFilter
actions:
- typeKind: ApplyCommentAction
comment: filter was applied
View definition of PostFilter for .NET integration.
The following filters are related to this filter:
postFilter is a convenience wrapper around methodFilter with the verb fixed to POST. The rule file stays shorter and clearer. Use methodFilter when you need a regex, a custom verb, or to match several verbs at once.
Yes. HTTP methods are normalized before comparison, so post, Post and POST all match.
Yes. Set inverted: true to select every exchange that is not a POST request.
postFilter matches by verb only. formRequestFilter matches by Content-Type (application/x-www-form-urlencoded or multipart/form-data) regardless of verb. Use postFilter for the verb, formRequestFilter for the body shape.