You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/azure-cache-for-redis/cache-aspnetcore-output-cache-provider.md
+2-12Lines changed: 2 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,7 +7,7 @@ ms.service: cache
7
7
ms.devlang: csharp
8
8
ms.custom: devx-track-csharp
9
9
ms.topic: how-to
10
-
ms.date: 06/13/2024
10
+
ms.date: 06/14/2024
11
11
12
12
#customer intent: As a cloud developer, I want to understand core output caching via Azure Cache for Redis so that I can implement it for storing page output.
13
13
---
@@ -24,16 +24,6 @@ The benefits of using Azure Cache for Redis as your output cache include:
24
24
- Saving web server memory resource utilization by storing cached content in an external Redis database.
25
25
- Improving web application resiliency by persisting cached content in an external Redis database in the scenario of server failover or restart.
26
26
27
-
Using the Redis option for output caching provides performance and storage optimizations over custom implementations of other output caching providers.
28
-
29
-
<!-- PM input needed: original text - "The Redis output caching implementation includes performance and storage optimizations comparing with custom implementations of the Output Caching middleware providers."
30
-
31
-
What I think it means: Using the Redis option for output caching provides performance and storage optimizations over custom implementations of other output caching providers.
32
-
33
-
This almost sounds a bit to much like marketing and maybe we should omit it. Will it always be true? Do we have benchmarks that quantitatively show this? Or am I missing the real technical advantage?
34
-
35
-
-->
36
-
37
27
You can use the output caching middleware in all types of ASP.NET Core apps: minimal API, web API with controllers, Model-View-Controller (MVC), and Razor Pages. For a detailed walkthrough of output caching syntax and features, see [Output caching middleware in ASP.NET Core](/aspnet/core/performance/caching/output).
38
28
39
29
## Prerequisites
@@ -140,7 +130,7 @@ It's a security best practice to avoid storing passwords in clear text in source
140
130
141
131
1. Obtain the Azure Cache for Redis connection strings by using the Azure portal.
142
132
143
-
You can find the connection string for Redis OSS by selecting **Authentication** on the **Resource** menu. Here's an example string: `<Azure_redis_name>.redis.cache.windows.net:6380,password=<Azure_redis_primary_accesskey>,ssl=True,abortConnect=False`.
133
+
You can find the connection string for open source Redis tiers by selecting **Authentication** on the **Resource** menu. Here's an example string: `<Azure_redis_name>.redis.cache.windows.net:6380,password=<Azure_redis_primary_accesskey>,ssl=True,abortConnect=False`.
144
134
145
135
You can find the access keys for Redis Enterprise by selecting **Access keys** on the **Resource** menu. The connection string can be derived with other Redis information from the **Overview** section of the **Resource** menu. Here's an example string: `<Azure_redis_name>.<Azure_region>.redisenterprise.cache.azure.net:10000,password=<Azure_redis_primary_accesskey>,ssl=True,abortConnect=False`.
0 commit comments