Hi all!
I am developing a website in ASP.NET (C#) and Microsoft Content
Management Server 2002 (a.k.a. MCMS 2002). MCMS 2002 creates each page
on the fly and returns by default always an HTTP status code 200, also
when the page has not been modified since the last request from the
client.
This causes performance problems when indexing our site. Incremental
updates are full updates since the status code 200 is returned and not
304 (Not Modified). For this problem Microsoft published a knowledge
base article (see link below). In this article code is displayed to
return a '304' in case of unmodified pages.
The article also states that only downlevel caching is possible using
the code:
Response.Cache.SetCacheability(System.Web.HttpCacheability.Public)
I would like to cache pages on the server:
Response.Cache.SetCacheability(System.Web.HttpCacheability.Server
or
Response.Cache.SetCacheability(System.Web.HttpCacheability.ServerAndPrivate
It seems that using server cache prevents sending a 'if-modified-since'
in the header of the HTTP request.
Does anybody have ideas why only downlevel cache can be used in this
case (if you didn't give up reading this long explanation ;-))?
http://support.microsoft.com/default.aspx?scid=kb;en-us;832432
Thanks in advance!
Cheers,
Stan.
Joerg Jooss - 20 Oct 2005 22:14 GMT
> Hi all!
>
[quoted text clipped - 31 lines]
>
> http://support.microsoft.com/default.aspx?scid=kb;en-us;832432
A conditional GET requires a local copy on the client in order to be
meaningful. You just cannot ask a server "do you have a newer copy" if
there's no local copy to compare to.
Cheers,

Signature
http://www.joergjooss.de
mailto:news-reply@joergjooss.de
stanevers@hotmail.com - 21 Oct 2005 12:29 GMT
Hi Joerg,
That sounds plausible! Thanx for your reply!
Greetz,
Stan.