Is there any Http Caching for ASP.Net Web Forms?

Question

I have an ASP.Net Web Forms application. The blog post "CacheCow Series - Part 0: Getting started and caching basics" mentions that Output Caching uses HttpRuntime.Cache behind the scene -hence not HTTP caching. The request reaches the server and cached response is sent from the server (when the valid cached output is avaialble on the server). So the entire content is sent across the wire.

Is there any HTTP Caching available for ASP.Net Web Forms (where response content is not sent from the server, if cache is valid; but the client takes it from it's HTTP Cache after getting validity information (only) from the server)?

REFERENCES

More reference: HOW-TO: HTTP CACHING FOR RESTFUL & HYPERMEDIA APIS — LCJ
– LCJ, Commented Aug 18, 2016 at 21:08

Niels V · Accepted Answer · 2016-08-18 10:14:31Z

1

+50

Actually the OutputCache directive is used for both Client as Server side caching. When you set the Location of that directive to Any, Client, Downstream or ServerAndClient, proper cache response headers are set such that browsers or proxies won't request the same page again and serve the cached version of your page. But keep in mind that those clients are free to request those pages again.

Location options with their Cache-Control headers after setting directive: <%@ OutputCache Location="XXX" Duration="60" VaryByParam="none" %>

Client: private, max-age=60
Downstream: public, max-age=60
Any: public
ServerAndClient: private, max-age=60
Server: no-cache
No output directive: private

answered Aug 18, 2016 at 10:14

Niels V

9958 silver badges11 bronze badges

Sign up to request clarification or add additional context in comments.

2 Comments

LCJ Over a year ago

Please read max-age. I guess, all the approaches you mentioned tells the client to consider data as stale after a time period. It doesn't validate whether the data actually changed by sending a request to server, using a mechanism like ETag .

Niels V Over a year ago

No, it doesn't do ETag validation out of the box. IIS does it for static content, but ASP.NET webforms not. But please refrase your question what you actually are looking for.

Collectives™ on Stack Overflow

Is there any Http Caching for ASP.Net Web Forms?

1 Answer 1

2 Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

2 Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related