We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
server-timing
Forwarded from downstream issue:
Linux
v16.14.2
3.0.0
1.0.0
[email protected]
vite
nitro
-
Default nuxt deploy from nuxt.new:
nuxt.new
Nuxt deploy with nitro -> timing -> false
nitro -> timing -> false
server-timing : -;dur=0;desc="Generate"
-;dur=0;desc="Generate"
Regardless of the choice, the timing header is always returned in the response headers. Where such a header should not be returned by default.
No response
The text was updated successfully, but these errors were encountered:
Solved in #823 :) @danielroe please close. There's no point in keeping open issues for resolved issues :)
Sorry, something went wrong.
Thank you for spotting!
No branches or pull requests
Forwarded from downstream issue:
server-timing
header is always returned even when turned off nuxt/nuxt#15660 by @oritwoenEnvironment
Linux
v16.14.2
3.0.0
1.0.0
[email protected]
vite
nitro
-
-
Reproduction
Default nuxt deploy from
nuxt.new
:Nuxt deploy with
nitro -> timing -> false
Response Header:
server-timing
:-;dur=0;desc="Generate"
Describe the bug
Regardless of the choice, the timing header is always returned in the response headers. Where such a header should not be returned by default.
Additional context
No response
Logs
No response
The text was updated successfully, but these errors were encountered: