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.
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
rejectWithMessageAction
This action has no specific characteristic
The following examples apply this action to any exchanges
Block with a plain text message.
rules:
- filter:
typeKind: AnyFilter
actions:
- typeKind: RejectWithMessageAction
statusCode: 403
message: Access to this site is blocked by corporate policy
contentType: text/plain
Block with an HTML page.
rules:
- filter:
typeKind: AnyFilter
actions:
- typeKind: RejectWithMessageAction
statusCode: 403
message: <html><body><h1>Blocked</h1><p>This site has been blocked for security reasons.</p></body></html>
contentType: text/html
Block with a JSON response (for APIs).
rules:
- filter:
typeKind: AnyFilter
actions:
- typeKind: RejectWithMessageAction
statusCode: 403
message: '{"error": "forbidden", "message": "This endpoint is blocked"}'
contentType: application/json
View definition of RejectWithMessageAction for .NET integration.
The following actions are related to this action:
What is rule file? | How to integrate rule with Fluxzy Desktop? | How to integrate rule with Fluxzy CLI?