Trace not found when some special chars are in the url
Open
Nobody has claimed this yet.
bug
- Dominant language
- Python
- Stars
- 39.9k
- Forks
- 3.4k
- Avg merge
- 7h 27m
- Merged PRs (30d)
- 222
Description
Bug Description
Testing out LLM traces and I get 404 on some traces which are obviously there
When clicking on one of them it says:
Using custom distinct id, event name, etc
The url is something in this format:
/llm-analytics/traces/[string]:[string]/[string]:[number]:[id]
Not sure if the : or the / trips up the routing.
How to reproduce
Additional context
Debug info
- [ ] PostHog Cloud, Debug information: [please copy/paste from https://us.posthog.com/settings/project-details#variables or https://eu.posthog.com/settings/project-details#variables]
- [ ] PostHog Hobby self-hosted with `docker compose`, version/commit: [please provide]
- [ ] PostHog self-hosted with Kubernetes (deprecated, see [`Sunsetting Kubernetes support`](https://posthog.com/blog/sunsetting-helm-support-posthog)), version/commit: [please provide]
Contributor 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.
Research direction
No source file, test, or concrete reproduction steps are named. Start by reproducing the 404 from a trace URL containing the reported colon, slash, and custom identifiers, then trace the route handling for /llm-analytics/traces. Done means affected traces open successfully and a regression check covers the special-character URL.
Written by the indexing model from the issue text.
Assessment
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100