forked from praxis-proxy/praxis
-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathfailure-mode.yaml
More file actions
47 lines (42 loc) · 1.28 KB
/
Copy pathfailure-mode.yaml
File metadata and controls
47 lines (42 loc) · 1.28 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
# Per-Filter Failure Mode
#
# Demonstrates open and closed failure handling for filters.
#
# Each filter can specify `failure_mode` to control what happens when
# the filter returns an error:
#
# closed (default) — abort the request and return 500
# open — log the error and continue to the next filter
#
# Use `open` for best-effort / observability filters where availability
# matters more than enforcement. Use `closed` (or omit the field) for
# security-critical filters that must never be bypassed.
#
# Usage:
# cargo run -p praxis-proxy -- -c examples/configs/pipeline/failure-mode.yaml
listeners:
- name: default
address: "127.0.0.1:8080"
filter_chains:
- main
filter_chains:
- name: main
filters:
# Observability: best-effort — if logging fails, keep serving.
- filter: access_log
failure_mode: open
# Security: must not be bypassed — explicit closed.
- filter: ip_acl
failure_mode: closed
allow:
- "0.0.0.0/0"
# Routing: default failure_mode (closed).
- filter: router
routes:
- path_prefix: "/"
cluster: backend
- filter: load_balancer
clusters:
- name: backend
endpoints:
- "127.0.0.1:3000"