You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
# Group HTTP methods by endpoint for legacy behavior (default: false)
282
284
group_methods_by_endpoint = false
283
285
286
+
```
287
+
Notes on exclusion patterns
288
+
289
+
- Method prefixes (optional): If a pattern starts with one or more HTTP method names followed by whitespace, the pattern applies only to those methods. Methods may be comma-separated and are matched case-insensitively. Example: `GET,POST /users/*`.
290
+
- Path-only patterns (default): If no method is specified the pattern applies to all methods for the matching path (existing behaviour).
291
+
- Wildcards: Use `*` to match any characters in the path portion (not a regex; dots and other characters are treated literally unless `*` is used).
292
+
- Negation: Prefix a pattern with `!` to override earlier exclusions and re-include a path (or method-specific path). Negations can also include method prefixes (e.g. `!GET /admin/health`).
293
+
- Matching: Patterns are tested against both the full `METHOD /path` string and the `/path` portion to remain compatible with existing configurations.
294
+
295
+
Examples (pyproject or CLI):
296
+
297
+
- Exclude the `/health` path for all methods:
298
+
299
+
```toml
300
+
exclusion_patterns = ["/health"]
301
+
```
302
+
303
+
- Exclude only GET requests to `/health`:
304
+
305
+
```toml
306
+
exclusion_patterns = ["GET /health"]
307
+
```
308
+
309
+
- Exclude GET and POST for `/users/*` but re-include GET /users/42:
0 commit comments