Skip to content

fix(sandbox): strip query string from L7 path matching #614

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
johntmyers wants to merge 1 commit into from
+6 −0
Closed

fix(sandbox): strip query string from L7 path matching #614

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions docs/reference/policy-schema.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -198,6 +198,12 @@ Used when `access` is not set. Each rule explicitly allows a method and path com
| `allow.path` | string | Yes | URL path pattern. Supports `*` and `**` glob syntax. |
| `allow.query` | map | No | Query parameter matchers keyed by decoded param name. Matcher value can be a glob string (`tag: "foo-*"`) or an object with `any` (`tag: { any: ["foo-*", "bar-*"] }`). |

**Path matching behavior:**

- Path rules match only the path component of the request URI (everything before `?`).
- Query strings are not evaluated by path rules. A rule with `path: /api/v1/download` matches both `/api/v1/download` and `/api/v1/download?slug=my-skill&version=1.0`.
- Glob patterns use `/` as the segment delimiter. `*` matches within a single segment, `**` matches across segments.

Example with rules:

```yaml
Expand Down
Loading