On 8/12/07, Robert Cummings <robert@xxxxxxxxxxxxx> wrote: > On Sat, 2007-08-11 at 22:11 -0500, Richard Lynch wrote: > > You don't do it there. > > > > You do whatever it is you have to do in the URL before you re-direct. > > > > Though I guess if you want different output on that page, you would > > need to set something somewhere, be it session, database, or a cookie. > > I think you're missing the point Richard. Yes you can detect the meta > redirect or manual refresh using your method. But only the first can be > detected because when the page is served up to the browser again either > the special meta redirect URL is active, non special normal URL is > active, or a super special I'm redirecting but don't count me URL is > active. Now what happens when the user does a manual refresh again? It's > not about output, it's about detecting subsequent refreshes and > determining again the source of the refresh. You must have some kind of > session tracking system in place, be it a regular session or a database > query that can check if an ID was already detected that indicates to > discount the page load from any statistics. > > Cheers, > Rob. I think you Rob missed a part of Richard's first reply: "You would then need to re-direct back to the URL *without* the GET parameter from_meta_tag=1 so that their refresh button would not be going to that URL with from_meta_tag in it." Tijnema -- Vote for PHP Color Coding in Gmail! -> http://gpcc.tijnema.info -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
