daohualiuxiang
/
AspNetCore.Docs
mirror of https://github.com/dotnet/AspNetCore.Docs.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Blazor JS file cache/no-cache guidance (#23235)

pull/23238/head
Luke Latham 2021-09-08 08:36:39 -05:00 committed by GitHub
parent 41f813db41
commit 926c398fab
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 58 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

58
aspnetcore/blazor/javascript-interoperability/index.md
View File

@ -176,6 +176,25 @@ JS isolation provides the following benefits:
For more information, see <xref:blazor/js-interop/call-javascript-from-dotnet#javascript-isolation-in-javascript-modules>.
## Cached JavaScript files
JavaScript (JS) files and other static assets aren't generally cached on clients during development in the [`Development` environment](xref:fundamentals/index#environments). During development, static asset requests include the [`Cache-Control` header](https://developer.mozilla.org/docs/Web/HTTP/Headers/Cache-Control) with a value of [`no-cache`](https://developer.mozilla.org/docs/Web/HTTP/Headers/Cache-Control#cacheability) or [`max-age`](https://developer.mozilla.org/docs/Web/HTTP/Headers/Cache-Control#expiration) with a value of zero (`0`).
During production in the [`Production` environment](xref:fundamentals/index#environments), JS files are usually cached by clients.
To disable client-side caching in browsers, developers usually adopt one of the following approaches:
* Disable caching when the browser's developer tools console is open. Guidance can be found in the developer tools documentation of each browser maintainer:
* [Chrome DevTools](https://developer.chrome.com/docs/devtools/)
* [Firefox Developer Tools](https://developer.mozilla.org/docs/Tools)
* [Microsoft Edge Developer Tools overview](/microsoft-edge/devtools-guide-chromium/)
* Perform a manual browser refresh of any webpage of the Blazor app to reload JS files from the server. ASP.NET Core's HTTP Caching Middleware always honors a valid no-cache [`Cache-Control` header](https://developer.mozilla.org/docs/Web/HTTP/Headers/Cache-Control) sent by a client.
For more information, see:
* <xref:blazor/fundamentals/environments>
* <xref:performance/caching/response>
::: moniker-end
::: moniker range=">= aspnetcore-5.0 < aspnetcore-6.0"
@ -343,6 +362,25 @@ JS isolation provides the following benefits:
For more information, see <xref:blazor/js-interop/call-javascript-from-dotnet#javascript-isolation-in-javascript-modules>.
## Cached JavaScript files
JavaScript (JS) files and other static assets aren't generally cached on clients during development in the [`Development` environment](xref:fundamentals/index#environments). During development, static asset requests include the [`Cache-Control` header](https://developer.mozilla.org/docs/Web/HTTP/Headers/Cache-Control) with a value of [`no-cache`](https://developer.mozilla.org/docs/Web/HTTP/Headers/Cache-Control#cacheability) or [`max-age`](https://developer.mozilla.org/docs/Web/HTTP/Headers/Cache-Control#expiration) with a value of zero (`0`).
During production in the [`Production` environment](xref:fundamentals/index#environments), JS files are usually cached by clients.
To disable client-side caching in browsers, developers usually adopt one of the following approaches:
* Disable caching when the browser's developer tools console is open. Guidance can be found in the developer tools documentation of each browser maintainer:
* [Chrome DevTools](https://developer.chrome.com/docs/devtools/)
* [Firefox Developer Tools](https://developer.mozilla.org/docs/Tools)
* [Microsoft Edge Developer Tools overview](/microsoft-edge/devtools-guide-chromium/)
* Perform a manual browser refresh of any webpage of the Blazor app to reload JS files from the server. ASP.NET Core's HTTP Caching Middleware always honors a valid no-cache [`Cache-Control` header](https://developer.mozilla.org/docs/Web/HTTP/Headers/Cache-Control) sent by a client.
For more information, see:
* <xref:blazor/fundamentals/environments>
* <xref:performance/caching/response>
::: moniker-end
::: moniker range="< aspnetcore-5.0"
@ -499,4 +537,24 @@ The `{webassembly|server}` placeholder in the preceding markup is either `webass
For more information on Blazor startup, see <xref:blazor/fundamentals/startup>.
## Cached JavaScript files
JavaScript (JS) files and other static assets aren't generally cached on clients during development in the [`Development` environment](xref:fundamentals/index#environments). During development, static asset requests include the [`Cache-Control` header](https://developer.mozilla.org/docs/Web/HTTP/Headers/Cache-Control) with a value of [`no-cache`](https://developer.mozilla.org/docs/Web/HTTP/Headers/Cache-Control#cacheability) or [`max-age`](https://developer.mozilla.org/docs/Web/HTTP/Headers/Cache-Control#expiration) with a value of zero (`0`).
During production in the [`Production` environment](xref:fundamentals/index#environments), JS files are usually cached by clients.
To disable client-side caching in browsers, developers usually adopt one of the following approaches:
* Disable caching when the browser's developer tools console is open. Guidance can be found in the developer tools documentation of each browser maintainer:
* [Chrome DevTools](https://developer.chrome.com/docs/devtools/)
* [Firefox Developer Tools](https://developer.mozilla.org/docs/Tools)
* [Microsoft Edge Developer Tools overview](/microsoft-edge/devtools-guide-chromium/)
* Perform a manual browser refresh of any webpage of the Blazor app to reload JS files from the server. ASP.NET Core's HTTP Caching Middleware always honors a valid no-cache [`Cache-Control` header](https://developer.mozilla.org/docs/Web/HTTP/Headers/Cache-Control) sent by a client.
For more information, see:
* <xref:blazor/fundamentals/environments>
* <xref:performance/caching/response>
::: moniker-end