chore: Add cache-control response header for docfx serve
#10891
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR intended to fix browser cache related problems when using
docfx servecommand.Background
Currently
docfx servecommand using defaultUseStaticFilessetting.So
Cache-Controlheader is not written. And browser's default heuristic caching policy is used.When using
docfx servecommand, sometimes cached contents are shown.And it need to force refresh cache with
Ctrl+F5orDisable Cacheon Developer Tools.What's changed in this PR
cache-control: max-age=60is added on response header.When max-age is expired. Browser request content to server with ETag.
If there is no changes.
304 Not Modifiedresponse is returned.Therefore, the load on the
Kestrelside is not expected to be significant when usingcache-control: max-age=60setting.