Question 277576 in ASP.NET Question posted in
The official documentation can be found here.

Why doesn't output caching middleware recognize the root controller URL in ASP.NET Core MVC

I have an ASP.NET application. The Index method that loads the page performs queries on a database. These queries are expensive and that datasets change infrequently, so this is a perfect use case for caching.

I added the output caching middleware to my Program.cs file.

I want to cache the server-side output, so I added flags to my Index functions:

[HttpGet]
[OutputCache(Duration = 43200, NoStore = false)]
public IActionResult Index()
{
    some code...
}

When I access the page using: https://web.app.com/Controller/Index the page caches as expected. However, when I use: https://web.app.com/Controller/ (which routes to the same endpoint) the page fails to cache, even after refreshing.

I understand that each unique URL should be cached by the server. Is there any reason why the root URL is being ignored?

Tags:

2

Answers


  1. Chosen as BEST ANSWER
    0

    I changed my app setup in Program.cs from:

    app.MapControllerRoute(
    name: "default",
    pattern: "{controller=Home}/{action=Index}/{id?}");

    to:

    app.MapDefaultControllerRoute();

    For some reason, this fixed the problem--the root URL for the controller is now being cached.

    Microsoft documentation states that MapDefaultControllerRoute() is a convenience method that is equivalent to the first code snippet.

    If anyone knows why this would make a difference, feel free to comment.


  2. 0

    Perhaps the reason is ‘/’ character in the end of "https://web.app.com/Controller/". Try to get rid of it or use redirection:

    var options = new RewriteOptions().AddRedirect("^(.*[^/])$", "$1/");
app.UseRewriter(options);
    Login or Signup to reply.
Please signup or login to give your own answer.

Back To Top
Search