headers seem to be off limits for the time being
On Monday, October 6, 2003, at 01:09 PM, Scott Cadillac wrote:
Hi Roland,
In the Advanced Training document you got in San Diego, there is a section
on "Prevent Caching of Dynamic Content" which includes this code snippet.
<@ASSIGN request$httpHeader VALUE="HTTP/1.1 <@HTTPSTATUSCODE> <@HTTPREASONPHRASE><@CRLF>Content-Type: text/html<@CRLF>X-Witango: <@VERSION> <@PLATFORM><@CRLF>Cache-Control: no-cache, max-age=0, must-revalidate, proxy-revalidate<@CRLF>Pragma: no-cache<@CRLF><@USERREFERENCECOOKIE><@CRLF>">
(Witango v5 and up only)
I've been using these HTTP property settings in one form or another for a
very long time and rarely ever have problems.
HTTP is a standard, but loosely enforced with regards to proxies, firewalls
and other cache stores so you'll probably never find a single definitive
solution.
It's important to note, that when assigning your own custom HTTP Response
Header in Witango, that you included the <@USERREFERENCECOOKIE> Meta Tag -
please read up on this in the Studio Help.
Hope this is what you are looking for. Cheers.....
Scott Cadillac, Witango.org - http://witango.org 403-281-6090 - [EMAIL PROTECTED] -- Information for the Witango Developer Community ---------------------
XML-Extranet - http://xmlx.ca 403-281-6090 - [EMAIL PROTECTED] -- Well-formed Development (for hire) ---------------------
-----Original Message----- From: Roland A. Dumas [mailto:[EMAIL PROTECTED] Sent: Monday, October 06, 2003 12:48 PM To: WiTango List Subject: Witango-Talk: no cache headers
what's the definitive most effective combo plate of headers to thwart caching?
______________________________________________________________ __________ TO UNSUBSCRIBE: Go to http://www.witango.com/maillist.taf
_______________________________________________________________________ _
TO UNSUBSCRIBE: Go to http://www.witango.com/maillist.taf
________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/maillist.taf
