The content clients send . and .. as path segments
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 78/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- csharp, typescript
- Domain
- backend-api-design, security
Research direction
Start with segment() in clients/typescript/src/client.ts and Segment() in src/FluentCMS.Client/FluentCmsClient.cs, then read the tests for both clients. Check how each client handles empty, . and .. path values, including %2e forms. Add tests showing both clients throw for the specified segments; done when the acceptance criteria pass in both clients.
Written by the indexing model from the issue text.
Description
Problem
segment() in clients/typescript/src/client.ts:166-172 and Segment() in src/FluentCMS.Client/FluentCmsClient.cs:157-191 percent-encode values, but . and .. pass unchanged and URL resolution removes them: getBy("article", "slug", "..") requests …/api/delivery/v1/article/by/, and a type .. reaches another route with the client's key. A front end that passes a route parameter into the client can be steered to another endpoint.
Proposal
Refuse empty, . and .. segments (and %2e forms) in both clients.
Acceptance
- Both clients throw for
.and..in any segment - Tests in both clients
Found in the code review of 17 Nov 2026 (S7).
- Dominant language
- C#
- Stars
- 569
- Forks
- 107
- Avg merge
- 2h 49m
- Merged PRs (30d)
- 397
Getting set up
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from fluentcms/FluentCMS
-
area:host area:operations type:bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
area:build security type:chore
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
area:content security type:bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
area:build type:bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
area:admin area:testing type:chore
Difficulty 4/5 3-5 days Newbie friendliness 48/100
Maintainers usually reply within 1 day
All issues in fluentcms/FluentCMS
Similar issues
-
clawsweeper:fix-shape-clear clawsweeper:queueable-fix clawsweeper:source-repro impact:ux-friction issue-rating: 🦞 diamond lobster no-stale P2
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
openclaw/openclaw-windows-node#2287 · 2 comments · 1 reaction ·
Maintainers usually reply within 1 day
-
kind:ux needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
elsa-workflows/elsa-foundation#4742 ·
Maintainers usually reply within 1 day
-
priority:P2
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
enhancement good first issue help wanted new-language
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
approved area: ui bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day