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:

SKU Question (1999) WebStar Secure on other machine (1997) Need help with emailer- 2 issues (1997) three cart questions (1997) 2.0 Info (1997) Hello??? (1997) Hierarchy of form/text/math variables (renamed thread) (2000) WebCat2 - Getting to the browser's username/password data (1997) [WebDNA] 3-5 GB of native WebDNA db in RAM?, else MySQL w/WebDNA [SQL] tags, else skip WebDNA altogether? (2009) Help! WebCat2 bug (1997) Search design (1997) WebMerchant Error (1998) selectively replacing records within a [founditems] (2000) Moment of Thanks (1997) Coding Style (2000) Form Validation (2000) grep question - how to strip spaces from the beginning ofa string? (2002) Comments in db? (1997) Re:no [search] with NT (1997) Request for help on a new *automated* WebCatalog function ... (1998)