Seems I am the main poster on my own question but since this was rather urgent I called Todd who was very helpful and also spoke with Ian who had at least one other idea.
So here is the current status and this might be useful for folks. 1. Ian seems to feel as I did that as long as there is a user reference argument and nc=(random number here) then the proxy server will not cache the pages. The document Todd referred people too. <http://www.mnot.net/cache_docs/> Seems to suggest this might not work because the proxy server almost never reads the HTML. Of course since this is part of the URL I would think it would work. Seems to be some debate on that one but also seems like a good way to go with your code. 2. Since this is IIS I went into the HTTP header and tab under properties and clicked on enable expiration. You would think you could use immediate but it in fact does not change the HTTP header. I clicked on customer. Named it Expires and in named value pair Fri, 30 Oct 1998 14:19:41 GMT ( In actually used today at 6AM but anything in the past will do as long as the syntax, spacing and format is right) It now send the right HTTP header so it should force the proxy to load. 3. You could also create SSL and make everything HTTPS because it never caches encrypted pages but that seems like overkill unless your doing transactions. 4. Ian pointed out that the default page being login.taf means that the 1st hit has no userreferance and no nc= and that could cause a problem. I am thinking of adding a hTML redirect page as the default and having it take you to login with the arguments in the redirect or else a static page up from with login and sign up and those links carrying the arguments. That way 1st hit to a taf has a userreferance and nc= as part of the string. I guess I have to make them tml files for it to work right. Not sure about this myself. That's the latest. Hopefully others will eventually chime in. on 6/6/02 4:28 PM, Dan Stein at [EMAIL PROTECTED] wrote: > Despite the usually fool proof random number generator I am having proxy > server problems like those described in a previous thread. Todd's suggestion > of the web site with cache tutorial was very helpful but of the code > suggested there what is necessary in the HTTP header. I modified the HTTP > header through the config taf > The example uses this > > > HTTP/1.1 200 OK > Date: Fri, 30 Oct 1998 13:19:41 GMT > Server: Apache/1.3.3 (Unix) > Cache-Control: max-age=3600, must-revalidate > Expires: Fri, 30 Oct 1998 14:19:41 GMT > Last-Modified: Mon, 29 Jun 1998 02:28:12 GMT > ETag: "3e86-410-3596fbbc" > Content-Type: text/html > > > I only used this > > HTTP/1.1 200 OK > Date: Fri, 30 Oct 1998 13:19:41 GMT > Expires: Fri, 30 Oct 1998 14:19:41 GMT > > And I put in those dates. Is that valid? > > -- Dan Stein Digital Software Solutions 799 Evergreen Circle Telford PA 18969 Land: 215-799-0192 Mobile: 610-256-2843 FMP, WiTango, EDI,SQL 2000 [EMAIL PROTECTED] www.dss-db.com ________________________________________________________________________ TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED] with unsubscribe witango-talk in the message body
