Re: Shownext on AOL

This WebDNA talk-list message is from

2003


It keeps the original formatting.
numero = 46953
interpreted = N
texte = >>Next, check to see whether or not the browser is caching pages it >>should not cache. If so, you may need to put a unique value into >>every link in your web site -- in order to force the browser to get >>the page from the server instead of from its cache. > >I have a Startat= thing in the URL. It shows either Startat=1 or >Startat=21. Is that not adequate as a unique value?No, that is not enough. Startat=1 and Startat=21 will come up time and time again when you perform the same search, and they probably already have come up repeatedly during your testing -- which is probably why you're seeing this problem. To fix it, just put something like:&u=[random][random][random][random][random]... into every URL in your site (just like you probably put &cart=[cart] into every URL) and it will prevent all browsers from reloading cached pages in your web site -- forever. >It could be AOHell's notorious server cache. I need to look into that more.It may be, since you're pretty sure it's not bad HTML. But placing a unique value in every URL will deal effectively with the AOL proxy server issues as well as the browser caching issue. From my understanding -- and in the absence of any reports to the contrary -- I have concluded that not even the most stupid browser or proxy server in the world will try to load or serve a page from its cache unless the entire URL looks *exactly* like one that's already been served. So all you really have to do is make every unique -- truly unique -- and you eliminate all caching problems ... which also means you never have to worry about using [setmimeheader] tags. Sincerely, Kenneth Grome--------------------------------------------------- WebDNA Professional Training and Development Center 175 J. Llorente Street +63 (32) 255-6921 Cebu City, Cebu 6000 kengrome@webdna.net Philippines http://www.webdna.net ---------------------------------------------------------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/ Associated Messages, from the most recent to the oldest:

    
  1. Re: Shownext on AOL (Glenn Busbin 2003)
  2. Re: Shownext on AOL (Kenneth Grome 2003)
  3. Re: Shownext on AOL (Donovan 2003)
  4. Re: Shownext on AOL (Glenn Busbin 2003)
  5. Re: Shownext on AOL (Kenneth Grome 2003)
  6. Re: Shownext on AOL (Velma Kahn 2003)
  7. Re: Shownext on AOL (Glenn Busbin 2003)
  8. Re: Shownext on AOL (Kenneth Grome 2003)
  9. Re: Shownext on AOL (Pedro Rivera 2003)
  10. Shownext on AOL (Glenn Busbin 2003)
>>Next, check to see whether or not the browser is caching pages it >>should not cache. If so, you may need to put a unique value into >>every link in your web site -- in order to force the browser to get >>the page from the server instead of from its cache. > >I have a Startat= thing in the URL. It shows either Startat=1 or >Startat=21. Is that not adequate as a unique value?No, that is not enough. Startat=1 and Startat=21 will come up time and time again when you perform the same search, and they probably already have come up repeatedly during your testing -- which is probably why you're seeing this problem. To fix it, just put something like:&u=[random][random][random][random][random]... into every URL in your site (just like you probably put &cart=[cart] into every URL) and it will prevent all browsers from reloading cached pages in your web site -- forever. >It could be AOHell's notorious server cache. I need to look into that more.It may be, since you're pretty sure it's not bad HTML. But placing a unique value in every URL will deal effectively with the AOL proxy server issues as well as the browser caching issue. From my understanding -- and in the absence of any reports to the contrary -- I have concluded that not even the most stupid browser or proxy server in the world will try to load or serve a page from its cache unless the entire URL looks *exactly* like one that's already been served. So all you really have to do is make every unique -- truly unique -- and you eliminate all caching problems ... which also means you never have to worry about using [setmimeheader] tags. Sincerely, Kenneth Grome--------------------------------------------------- WebDNA Professional Training and Development Center 175 J. Llorente Street +63 (32) 255-6921 Cebu City, Cebu 6000 kengrome@webdna.net Philippines http://www.webdna.net ---------------------------------------------------------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/ Kenneth Grome

DOWNLOAD WEBDNA NOW!

Top Articles:

Talk List

The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...

Related Readings:

urls (2005) Limit to variables being passed??? (1998) Search for dates greater than [date] (1997) URGENT: Can't email orders - HELP #2 (1998) Uploading out of FMP (2001) protect tag on NT IIS (1997) Classified (1999) RE: Credit card processing - UK (1997) $append (1998) too many nested ... problem (1997) Help! WebCat2 bug (Ben's input) (1997) self maintaining databases? (1998) Where's Cart Created ? (1997) Logout? (1998) Error:Too many nested [xxx] contexts (1997) Looping Search (2006) A multi-processor savvy WebCatalog? (1997) [WebDNA] Serial numbers and pricing for WebDNA 7.0 (2011) Using [Include] Context (1999) This Code Kills My WebCatalog Dead (2003)