Skip to content

Please add fix for "cache control directive for server side props" in v12 #58307

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

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

Jump to bottom
Closed
1 task done
billy-the-ape opened this issue Nov 10, 2023 · 2 comments
Closed
1 task done

Please add fix for "cache control directive for server side props" in v12 #58307

billy-the-ape opened this issue Nov 10, 2023 · 2 comments
Labels
bug Issue was opened via the bug report template. stale The issue has not seen recent activity.

Comments

@billy-the-ape
Copy link

billy-the-ape commented Nov 10, 2023 •
edited
Loading

Link to the code that reproduces this issue

#45301

To Reproduce

See #45301

Current vs. Expected behavior

Would love to get snyk to stop erroring without the effort of upgrading to v13

Verify canary release

  • I verified that the issue exists in the latest Next.js canary release

Provide environment information

Operating System:
      Platform: win32
      Arch: x64
      Version: Windows 11 Pro
    Binaries:
      Node: 20.9.0
      npm: N/A
      Yarn: N/A
      pnpm: N/A
    Relevant packages:
      next: 12.3.4
      eslint-config-next: 12.1.0
      react: 17.0.2
      react-dom: 17.0.2

Which area(s) are affected? (Select all that apply)

Not sure

Additional context

Can't tell if canary has fixed as snyk only runs on this repo when pushed to remote

Snyk link: https://security.snyk.io/vuln/SNYK-JS-NEXT-6032387
@billy-the-ape billy-the-ape added the bug Issue was opened via the bug report template. label Nov 10, 2023
@nextjs-bot
Copy link
Collaborator

This issue has been automatically marked as stale due to two years of inactivity. It will be closed in 7 days unless there’s further input. If you believe this issue is still relevant, please leave a comment or provide updated details. Thank you.

@nextjs-bot nextjs-bot added the stale The issue has not seen recent activity. label May 8, 2025
@nextjs-bot
Copy link
Collaborator

This issue has been automatically closed due to two years of inactivity. If you’re still experiencing a similar problem or have additional details to share, please open a new issue following our current issue template. Your updated report helps us investigate and address concerns more efficiently. Thank you for your understanding!

@nextjs-bot nextjs-bot closed this as not planned Won't fix, can't repro, duplicate, stale May 16, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Issue was opened via the bug report template. stale The issue has not seen recent activity.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@billy-the-ape @nextjs-bot