Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

https dev server does not use browser cache

See original GitHub issue

Describe the bug

http dev server

http request detail

The resource with Cache-Control: no-cache

tree_picker_first_request tree_picker_first_request_detail tree_picker_second_request tree_picker_second_request_detail

The resource with Cache-Control: max-age=3153

layout_first_request layout_first_request_detail layout_second_request layout_second_request_detail

https dev server

https request detail

The resource with Cache-Control: no-cache

tree_picker_first_request tree_picker_first_request_detail 6000,immutable` tree_picker_second_request tree_picker_second_request_detail

The resource with Cache-Control: max-age=3153

layout_first_request layout_first_request_detail layout_second_request layout_second_request_detail

Reproduction

System Info

Output of npx envinfo --system --npmPackages vite,@vitejs/plugin-vue --binaries --browsers:

  System:
    OS: Windows 10
    CPU: (8) x64 Intel(R) Xeon(R) CPU E3-1231 v3 @ 3.40GHz
    Memory: 10.20 GB / 19.92 GB
  Binaries:
    Node: 14.15.5 - D:\nodejs\node.EXE
    npm: 7.7.5 - D:\nodejs\npm.CMD
  Browsers:
    Edge: 44.19041.423.0
   Chrome: 89.0.4389.90

Used package manager: npm

Logs

Before submitting the issue, please make sure you do the following

Read the Contributing Guidelines.
Read the docs.
Check that there isn’t already an issue that reports the same bug to avoid creating a duplicate.
Provide a description in this issue that describes the bug.
Make sure this is a Vite issue and not a framework-specific issue. For example, if it’s a Vue SFC related bug, it should likely be reported to https://github.com/vuejs/vue-next instead.
Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.