Decide how to report exact routes that differ only in case
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 42/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- typescript
- Domain
- backend
Research direction
Start by locating build_route_table and the handling for duplicate exact routes and duplicate wildcards. Trace how skipped routes affect logging, failingRoutes, and metric series, then check existing tests for those cases. Done means the project has a documented decision for case-only pairs and behavior consistent with that decision.
Written by the indexing model from the issue text.
Description
Once route names match without regard to ASCII case (the SNI case-insensitivity PR), two exact routes that differ only in case, such as API.example.com and api.example.com, are one name. build_route_table keeps the last one, like two exact routes with the same spelling: the other is skipped with no log, no failingRoutes count and no metric series. Before, both were installed and each served its own spelling.
Central Manager and host-manager configure lowercase names, so neither produces such a pair. A hand-written symphony-server config could, and its earlier route would then stop serving with nothing reported.
Decide whether a case-only pair should log once and count in failingRoutes, the way a duplicate wildcard already does, or stay silent like a same-spelling exact duplicate.
Review-Deferral: 3568822582e342c0 severity=minor category=correctness
🤖 Generated by Claude Code (Claude Opus 5.5); posted via @dawsontoth.
- Dominant language
- TypeScript
- Stars
- 1
- Forks
- 0
- Avg merge
- 11h 49m
- Merged PRs (30d)
- 12
Getting set up
- No Dockerfile or Docker Compose file
- No 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 HarperFast/symphony
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
HarperFast/symphony#91 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
HarperFast/symphony#89 ·
Maintainers usually reply within 1 day
-
Mixed-case SNI forwarded to an older peer during a rolling upgrade can reach its wildcard routeOpen
Difficulty 4/5 3-5 days Newbie friendliness 49/100
HarperFast/symphony#93 ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 72/100
HarperFast/symphony#90 ·
Maintainers usually reply within 1 day
-
Don't route to a restarted upstream until it serves, not just acceptsPossibly taken @kriszyp claimed this 14 days ago. Open
HarperFast/symphony#84 · 1 assignee ·
Maintainers usually reply within 1 day
All issues in HarperFast/symphony
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
feature request needs triage
Difficulty 1/5 1-3 hours Newbie friendliness 69/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
solidjs/solid-docs#1716 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
thecodacus/pithagoras#380 ·
Maintainers usually reply within 1 day