The content clients send . and .. as path segments

Open Beginner friendly
#3,273 0 comments 0 reactions 0 assignees View on GitHub

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

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

area:sdk security type:bug

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

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from fluentcms/FluentCMS

All issues in fluentcms/FluentCMS

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.