Browse the Fluxzy Directive Library

Over 100 filters and actions to shape HTTP traffic exactly how you need it. Filters decide which traffic to target. Actions decide what to do with it.

What are directives?

Fluxzy uses a declarative rule system. A filter matches specific traffic (by host, method, header, status code, or dozens of other criteria). An action performs an operation on that traffic: modify headers, mock responses, add delays, set breakpoints, etc.

Combine a filter with one or more actions to create a rule. Rules are defined in YAML and work identically across Fluxzy Desktop, the CLI, and .NET integration. All directives are available in every Fluxzy tool, including the free Community Edition.

Read the rule file documentation for the full YAML syntax and examples.

{{ count }} directive found {{ count }} directives found

No matching directives. Try one of these:

Filters

absoluteUriFilter

Select exchanges according to URI (scheme, FQDN, path and query). Supports common string search option and regular expression.

View detail

agentLabelFilter

Select exchanges according to configured source agent (user agent or process) with a regular string search.

View detail

anyFilter

Select all exchanges

View detail

authorityFilter

Select exchange according to hostname and a port

View detail

commentSearchFilter

Select exchanges by searching a string pattern into the comment property.

View detail

contentTypeXmlFilter

Select exchanges having XML response body.

View detail

cssStyleFilter

Select exchanges having response content type mime matching css.

View detail

deleteFilter

Select exchanges with DELETE method

View detail

filterCollection

FilterCollection is a combination of multiple filters with a merging operator (OR / AND).

View detail

fontFilter

Select exchanges having response content type matching a font payload.

View detail

formRequestFilter

Select request sending 'multipart/form-data' or 'application/x-www-form-urlencoded' body. Filtering is made by inspecting value of `Content-Type` header

View detail

formUrlEncodedRequestFilter

Select request sending 'application/x-www-form-urlencoded' body. Filtering is made by inspecting value of `Content-Type` header

View detail

getFilter

Select exchanges with GET method

View detail

h11TrafficOnlyFilter

Select HTTP/1.1 exchanges only.

View detail

h2TrafficOnlyFilter

Select H2 exchanges only.

View detail

hasAnyCookieOnRequestFilter

Select exchanges having any request cookie

View detail

hasAuthorizationBearerFilter

Select exchanges having bearer token in authorization.

View detail

hasAuthorizationFilter

Select exchanges having authorization header.

View detail

hasCommentFilter

Select exchanges having comment.

View detail

hasCookieOnRequestFilter

Exchange having a request cookie with a specific name

View detail

hasRequestBodyFilter

Select request having body.

View detail

hasSetCookieOnResponseFilter

Search for a cookie value present in a `set-cookie` header response.If cookie name is not defined or empty, the filter will returns any cookie having the value.

View detail

hasTagFilter

Select exchanges having tag.

View detail

hostFilter

Select exchanges according to hostname (excluding port). To select authority (combination of host:port), use AuthorityFilter.

View detail

htmlResponseFilter

Select exchanges having HTML body. The content-type header is checked to determine if the content body is has text/html hint.

View detail

imageFilter

Select exchanges having response content type mime matching image.

View detail

ipEgressFilter

Select exchanges according to upstream IP address. Full IP notation is used from IPv6.

View detail

ipIngressFilter

Select exchanges according to client ip address. Full IP notation is used from IPv6.

View detail

isGrpcFilter

Select gRPC exchanges only. Filtering is made by inspecting value of `Content-Type` header.

View detail

isSecureFilter

Select secure exchange only (non plain HTTP).

View detail

isWebSocketFilter

Select websocket exchange.

View detail

jsonRequestFilter

Select request sending JSON body. Filtering is made by inspecting value of `Content-Type` header

View detail

jsonResponseFilter

Select exchanges having JSON response body. The content-type header is checked to determine if the content body is a JSON.

View detail

methodFilter

Select exchanges according to request method.

View detail

multipartDataRequestFilter

Select request sending 'multipart/form-data' body. Filtering is made by inspecting value of `Content-Type` header

View detail

networkErrorFilter

Select exchanges that fails due to network error.

View detail

patchFilter

Select exchanges with PATCH method

View detail

pathFilter

Select exchanges according to url path. Path includes query string if any. Path must start with `/`

View detail

postFilter

Select POST (request method) only exchanges.

View detail

processIdFilter

Select exchanges initiated by a process with the specified process ID. Process tracking must be enabled and the connection must originate from localhost.

View detail

processNameFilter

Select exchanges initiated by processes with the specified names. Process names are matched case-insensitively. On Windows, the .exe extension can be omitted. Process tracking must be enabled and the connection must originate from localhost.

View detail

protobufFilter

Select exchanges having a protobuf request or response body. Filtering is made by inspecting value of `Content-Type` header on both request and response.

View detail

protobufRequestFilter

Select requests sending a protobuf body. Filtering is made by inspecting value of `Content-Type` header.

View detail

protobufResponseFilter

Select exchanges having protobuf response body. The content-type header is checked to determine if the content body is protobuf.

View detail

putFilter

Select exchanges according to request method.

View detail

queryStringFilter

Select exchanges containing a specific query string. If `name` is not defined or empty, the search will be performed on any query string values.The search will pass if at least one value match.

View detail

requestHeaderFilter

Select exchanges according to request header values.

View detail

responseHeaderFilter

Select exchanges according to response header values.

View detail

statusCodeClientErrorFilter

Select exchanges that HTTP status code indicates a client error (4XX).

View detail

statusCodeFilter

Select exchanges according to HTTP status code.

View detail

statusCodeRedirectionFilter

Select exchanges that HTTP status code indicates a redirect (3XX).

View detail

statusCodeServerErrorFilter

Select exchanges that HTTP status code indicates a server/intermediary error (5XX).

View detail

statusCodeSuccessFilter

Select exchanges that HTTP status code indicates a successful request (2XX).

View detail

Actions

abortAction

Abort an exchange at the transport level. This action will close connection between fluxzy and client which may lead to depended exchanges to be aborted too.

View detail

addAuthorizationBasicAction

Add Authorization Basic to the request header.

View detail

addAuthorizationBearerAction

Add Authorization Bearer token to the request header.

View detail

addBasicAuthenticationAction

Add a basic authentication (RFC 7617) to incoming exchanges with an username and a password

View detail

addRequestHeaderAction

Append a request header.

View detail

addResponseHeaderAction

Append a response header. H2 pseudo header will be ignored.

View detail

applyCommentAction

Add comment to exchange. Comment has no effect on the stream behaviour.

View detail

applySessionAction

Apply captured session data to requests. Adds cookies from session store and optionally applies stored headers. Works in conjunction with CaptureSessionAction.

View detail

applyTagAction

Affect a tag to exchange. Tags are meta-information and do not alter the connection.

View detail

averageThrottleAction

Throttle and simulate bandwidth condition.

View detail

captureSessionAction

Capture session data from responses. Captures Set-Cookie headers and optionally other headers like Authorization. Can also capture cookies from request headers for intercepting ongoing sessions. Stored data can be replayed using ApplySessionAction.

View detail

changeRequestMethodAction

Alter the method of an exchange.

View detail

changeRequestPathAction

Change request uri path. This action alters only the path of the request. Request path includes query string.

View detail

clearSessionAction

Clear stored session data for a specific domain or all domains.

View detail

delayAction

Add a latency to the exchange.

View detail

deleteRequestHeaderAction

Remove request headers. This action removes every occurrence of the header from the request.

View detail

deleteResponseHeaderAction

Remove response headers. This action removes every occurrence of the header from the response.

View detail

fileAppendAction

Write to a file. Captured variable are interpreted.

View detail

forceHttp11Action

Force the connection between fluxzy and remote to be HTTP/1.1. This value is enforced by ALPN settings set during the SSL/Handshake handshake.

View detail

forceHttp2Action

Forces the connection between fluxzy and remote to be HTTP/2.0. This value is enforced when setting up ALPN settings during SSL/TLS negotiation.
The exchange will break if the remote does not support HTTP/2.0.
This action will be ignored when the communication is clear (h2c not supported).

View detail

forceRemotePortAction

Ignores the default port used by the current authority and use the provided port instead.

View detail

forceTlsVersionAction

Force the usage of a specific TLS version. Values can be chosen among : Tls, Tls11, Tls12, Tls13, Ssl3, Ssl2.
Forcing the usage of a specific TLS version can break the exchange if the remote does not support the requested protocol.

View detail

forwardAction

Forward request to a specific URL. This action makes fluxzy act as a reverse proxy. Unlike [SpoofDnsAction](https://www.fluxzy.io/rule/item/spoofDnsAction), host header is automatically set and protocol switch is supported (http to https, http/1.1 to h2, ...). The URL must be an absolute path.

View detail

impersonateAction

Impersonate a browser or client by changing the TLS fingerprint, HTTP/2 settings and headers.

View detail

injectHtmlTagAction

This action stream a response body and inject a text after the first specified html tag.This action can be used to inject a html code snippet after opening `` tag in any traversing html page.This action supports chunked transfer stream and the following body encodings: gzip, deflate, brotli and lzw.

View detail

mockedResponseAction

Reply with a pre-made response from a raw text or file

View detail

mountCertificateAuthorityAction

Reply with the default root certificate used by fluxzy

View detail

mountWelcomePageAction

Reply with fluxzy welcome page

View detail

noOpAction

An action doing no operation.

View detail

rejectAction

Block the request and return HTTP 403 Forbidden response. Use this action to explicitly deny access to specific resources. This is a simple blocking action with no configuration required.

View detail

rejectWithMessageAction

Block the request with a custom HTTP error response including a body message. Useful for providing detailed blocking reasons to end users. Supports text/plain, text/html, and application/json content types.

View detail

rejectWithStatusCodeAction

Block the request and return a custom HTTP error response. Allows specifying the status code (e.g., 403, 404, 502) to return to the client. The response body will contain the standard reason phrase for the status code.

View detail

removeCacheAction

Remove all cache directive from request and response headers. This will force the clientto ask the latest version of the requested resource.

View detail

removeResponseCookieAction

Remove a response cookie by setting the expiration date to a past date.

View detail

serveDirectoryAction

Serve a folder as a static web site. This action is made for mocking purpose and not production ready for a web site.

View detail

serveHttp11Action

Force the downstream connection (client-to-proxy) to use HTTP/1.1. When the global ServeH2 option is enabled, this action overrides it for matched exchanges by only advertising HTTP/1.1 during ALPN negotiation with the client.

View detail

setClientCertificateAction

Add a client certificate to the exchange. The client certificate will be used for establishing the mTLS authentication if the remote request it. The client certificate can be retrieved from the default store (my) or from a PKCS#12 file (.p12, pfx).
The certificate will not be stored in fluxzy settings and, therefore, must be available at runtime.

View detail

setJa3FingerPrintAction

Set a JA3 fingerprint of ongoing connection.

View detail

setRequestCookieAction

Add a cookie to request. This action is performed by adding/replacing `Cookie` header in request.

View detail

setResponseCookieAction

Add a response cookie. This action is performed by adding `Set-Cookie` header in response.

View detail

setUserAgentAction

Change the User-AgentThis action is used to change the User-Agent header of the request from a list of built-in user-agent values.

View detail

setVariableAction

Set a variable or update an existing

View detail

skipRemoteCertificateValidationAction

Skip validating remote certificate. Fluxzy will ignore any validation errors on the server certificate.

View detail

skipSslTunnelingAction

Instructs fluxzy to not decrypt the current traffic. The associated filter must be on OnAuthorityReceived scope in order to make this action effective.

View detail

spoofDnsAction

Fix statically the remote ip or port disregards to the dns or host resolution of the current running system. Use this action to force the resolution of a hostname to a fixed IP address.

View detail

stdErrAction

Write text to standard error. Captured variable are interpreted.

View detail

stdOutAction

Write text to standard output. Captured variable are interpreted.

View detail

updateRequestHeaderAction

Update and existing request header. If the header does not exists in the original request, the header will be added.
Use {{previous}} keyword to refer to the original value of the header.
Note Headers that alter the connection behaviour will be ignored.

View detail

updateResponseHeaderAction

Update and existing response header. If the header does not exists in the original response, the header will be added.
Use {{previous}} keyword to refer to the original value of the header.
Note Headers that alter the connection behaviour will be ignored.

View detail

upStreamProxyAction

Use an upstream proxy.

View detail

useCertificateAction

Use a specific server certificate. Certificate can be retrieved from user store or from a PKCS12 file

View detail

useDnsOverHttpsAction

Use DoH (DNS over HTTPS) to resolve domain names instead of the default DNS provided by the OS

View detail

Learn more about building rules

Rule file documentation Use with Fluxzy Desktop Use with CLI