| Groups | Blog | Home |
visual studio .net act : ACT and Client-side Cache ? ? ?
I am trying to use ACT to determine how caching HTML and images effects our
application's bandwidth and CPU requirements. However, It appears that ACT's default settings ignore client-side HTML and image caching. Is there a way to ensure that ACT does not request content that has already been retrieved and cached at the client? Mike -- mcp, mcse, mcsd, mcad.net, mcsd.net --
I am finding that ACT reads HTTP Headers but not Meta Tags thereby limiting
ACTs ability to test performance benefits of cached ASP pages. This could be a definit drawback for our testing purposes. Is there anything that allows ACT to parse the HTTP response, read Meta Tags, and then request request only non-cached pages? Research... 1. (http://msdn.microsoft.com/library/default.asp?url=/library/en-us/act/htm/actml_ref_bots.asp), “Since Application Center Test does not parse the HTTP response body, it does not use any robot information included in HTML META tagsâ€. 2. (http://msdn.microsoft.com/library/default.asp?url=/library/en-us/act/htm/actml_ref_rede.asp), “Application Center Test does not automatically parse the response body, so HTML META tag redirects are neither followed nor counted by the RedirectDepth property.†Distinction between HTTP Headers and Meta Tags... There are two primary ways to control cache in a web page, one is through the user of HTML Meta Tags and the other is through the use of HTTP Headers. Meta Tags Meta Tags are placed in an HTML document’s <HEAD> section by a web page author. The Meta Tags describe the content expiration period on the client. Meta Tags are typically preferred by web page authors as it gives them the most control over cache. There are gotchas: Meta tags do not cache images and some Internet Servers and most proxies do not honor Meta Tags. This is not true of the Microsoft IIS Server. Most browsers do honor the HTTP Meta Tag expiration date. HTTP Headers HTTP Headers are set through an Internet Server application such as Microsoft IIS and not by the web page author. In fact they can’t even be seen in the HTML document. The HTTP Cache Header primary purpose is to set an objects absolute time to expire, a time based on the last time that the client saw the object (last access time), or a time based on the last time the document changed on your server (last modification time). HTTP Headers are typically honored by all proxies, Internet servers, and browsers. HTTP Headers CANNOT be used to cache dynamically built ASP web pages. Summary HTTP Headers can cache images and static html and must be set via IIS. Meta Tags can cache only html and is set in the web page itself or programmatically at runtime. Meta Tags can not cache images. Mike
ACT does worst case scenario load testing. I cann't quitte figure out how
you can reliable predict the bandwith in case of caching as not only client-side but also proxies migth cache files. For sure aspx files are not cached if you don't handle them specially. [quoted text, click to view] "MLibby" wrote:
> I am finding that ACT reads HTTP Headers but not Meta Tags thereby limiting > ACTs ability to test performance benefits of cached ASP pages. This could be > a definit drawback for our testing purposes. Is there anything that allows > ACT to parse the HTTP response, read Meta Tags, and then request request only > non-cached pages? > > Research... > 1. > (http://msdn.microsoft.com/library/default.asp?url=/library/en-us/act/htm/actml_ref_bots.asp), > “Since Application Center Test does not parse the HTTP response body, it does > not use any robot information included in HTML META tagsâ€. > > 2. > (http://msdn.microsoft.com/library/default.asp?url=/library/en-us/act/htm/actml_ref_rede.asp), > “Application Center Test does not automatically parse the response body, so > HTML META tag redirects are neither followed nor counted by the RedirectDepth > property.†> > Distinction between HTTP Headers and Meta Tags... > There are two primary ways to control cache in a web page, one is through > the user of HTML Meta Tags and the other is through the use of HTTP Headers. > > Meta Tags > Meta Tags are placed in an HTML document’s <HEAD> section by a web page > author. The Meta Tags describe the content expiration period on the client. > Meta Tags are typically preferred by web page authors as it gives them the > most control over cache. There are gotchas: Meta tags do not cache images and > some Internet Servers and most proxies do not honor Meta Tags. This is not > true of the Microsoft IIS Server. Most browsers do honor the HTTP Meta Tag > expiration date. > > HTTP Headers > HTTP Headers are set through an Internet Server application such as > Microsoft IIS and not by the web page author. In fact they can’t even be seen > in the HTML document. The HTTP Cache Header primary purpose is to set an > objects absolute time to expire, a time based on the last time that the > client saw the object (last access time), or a time based on the last time > the document changed on your server (last modification time). HTTP Headers > are typically honored by all proxies, Internet servers, and browsers. HTTP > Headers CANNOT be used to cache dynamically built ASP web pages. > > Summary > HTTP Headers can cache images and static html and must be set via IIS. > Meta Tags can cache only html and is set in the web page itself or > programmatically at runtime. Meta Tags can not cache images. > > Mike
Don't see what you're looking for? Try a search.
|
| home · blog · groups | Questions? Comments? Contact the dn |