interesting, so how would that go w/ something like this? <@ASSIGN domain$httpHeader VALUE="HTTP/1.1 <@HTTPSTATUSCODE> <@HTTPREASONPHRASE><@CRLF>X-Witango: <@VERSION> <@PLATFORM><@CRLF>Content-Type: text/html<@CRLF>Cache-Control: no-cache, max-age=0, must-revalidate, proxy-revalidate<@CRLF>Pragma: no-cache<@CRLF><@USERREFERENCECOOKIE><@CRLF>">
would this be the ticket? <@ASSIGN domain$httpHeader VALUE="<@literal value='HTTP/1.1 <@HTTPSTATUSCODE> <@HTTPREASONPHRASE><@CRLF>X-Witango: <@VERSION> <@PLATFORM><@CRLF>Content-Type: text/html<@CRLF>Cache-Control: no-cache, max-age=0, must-revalidate, proxy-revalidate<@CRLF>Pragma: no-cache<@CRLF><@USERREFERENCECOOKIE><@CRLF>'>"> ----- Original Message ----- From: "John McGowan" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, March 02, 2004 3:10 PM Subject: Re: Witango-Talk: page caching > Alan, > > If you're going to be assigning that something other than the request > scope, you'd better make sure you use @literal, otherwise something like > <@userreferencecookie> will get evaluated when you assign the variable, > and never again. > > /John > > Alan Wolfe wrote: > > >Hey Scott, > > > >I found out you can assign this for user and domain scope as well (i > >verified w/ http look). Pretty cool! (: > > > >----- Original Message ----- > >From: "Scott Cadillac" <[EMAIL PROTECTED]> > >To: <[EMAIL PROTECTED]> > >Sent: Monday, March 01, 2004 10:04 AM > >Subject: Re: Witango-Talk: page caching > > > > > > > > > >>Hi Alan, > >> > >>Yes, if you have an include or TCF that is common to all your TAF files, > >>place the following assignment to instruct HTTP to not cache your content. > >> > >><@ASSIGN request$httpHeader VALUE="HTTP/1.1 <@HTTPSTATUSCODE> > >><@HTTPREASONPHRASE><@CRLF>X-Witango: <@VERSION> <@PLATFORM><@CRLF>Content- > >>Type: text/html<@CRLF>Cache-Control: no-cache, max-age=0, must- > >>revalidate, proxy-revalidate<@CRLF>Pragma: no- > >>cache<@CRLF><@USERREFERENCECOOKIE><@CRLF>"> > >> > >>Note: do not alter the "<@CRLF><@USERREFERENCECOOKIE><@CRLF>" part, this > >>ensures your special Witango session-cookie is properly managed. > >> > >>As well, as an extra measure to combat caching, I recommend adding a > >>unique value to all your links, something like: > >> > >><a href="some.taf?_function=hey&unique=<@RANDOM>">A link</a> > >> > >>Just so you know, session-cookies (session management) and caching are > >>not related, but the fact that you removed the <@USERREFERENCEARGUMENT> > >>from all your links means the link URL's are now "less" unique than they > >>were before - which can then cause any aggressive proxy or browsers to > >>cache some of your content. > >> > >>Cheers.... > >> > >>Scott Cadillac, > >>403-281-6090 ~ [EMAIL PROTECTED] > >>------------ > >>XML-Extranet ~ http://xmlx.ca ~ http://forums.xmlx.ca > >>Well-formed Programming in C# .NET, Witango, MSIE and XML > >>------------ > >>Witango ~ http://witango.org > >>EasyXSLT ~ http://easyxslt.ca > >>IIS Watcher ~ http://iiswatcher.ca > >>------------ > >> > >> > >>-----Original Message----- > >>From: "Alan Wolfe" <[EMAIL PROTECTED]> > >>To: <[EMAIL PROTECTED]> > >>Date: Mon, 1 Mar 2004 09:47:07 -0800 > >>Subject: Witango-Talk: page caching > >> > >> > >> > >>>over the weekend we took the userreference argument out of our tafs and > >>>things were working good, but now that mondays here, all our clients > >>>seem to have problems with their browsers caching the pages and making > >>>some wierd things happen because of that. > >>> > >>>is there a way to force a page not to be cached somehow via the http > >>>header or something? > >>>_______________________________________________________________________ > >>>_ > >>>TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf > >>> > >>> > >>________________________________________________________________________ > >>TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf > >> > >> > > > >________________________________________________________________________ > >TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf > > > > > > > > ________________________________________________________________________ > TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
