Server Timing Headers Contain Url Encoding
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 11.2k
- Forks
- 899
- Avg merge
- 2d 24m
- Merged PRs (30d)
- 40
Description
Environment
Node 18.15.0
Nitro 2.3.3
Reproduction
add this to your nuxt config file
nitro: {
timing: true
}
do a nuxt build, nuxt preview
inspect the response headers from the page hit in your browser
Describe the bug
When setting nitro.timing: true in nuxt.config.ts, the timing names returned are url encoded instead of normal.
Notice the %20 for spaces, and %2F for / etc..
Additional context
In Nuxt 2, these were spaces and they looked correct.
Logs
No response
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
Reproduce the issue by enabling nitro.timing in nuxt.config.ts, then running a Nuxt build and preview and inspecting the page response headers. Trace the timing-header handling from that configuration entry point; done means timing names containing spaces or slashes are returned normally rather than URL encoded.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nuxtjs, typescript
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100