Re: manual vs. meta refresh
| From: | Robert Cummings | Date: | Sat, 11 Aug 2007 02:57:34 +0000 |
| Subject: | Re: manual vs. meta refresh | ||
| References: | 1 2 3 | Groups: | php.general |
| Request: | Send a blank email to php-general+get-260674@lists.php.net to get a copy of this message | ||
On Sat, 2007-08-11 at 02:10 +0200, Tijnema wrote:
> On 8/11/07, Richard Lynch <ceo@l-i-e.com> wrote:
> > On Fri, August 10, 2007 1:26 pm, Kevin Murphy wrote:
> > > I doubt this, but is there any way to determine via PHP if a browser
> > > was refreshed automatically via a META tag vs the person clicking the
> > > refresh button?
> >
> > You could embed something in the META tag's URL such as:
> >
> > <meta http-equiv="refresh"
> > content="5;http://example.com?from_meta_tag=1"
> > >
> >
> > 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.
> >
> > Kind of kludgy, but should work
> Do you guys read other replies first before making a reply yourself?
> You're the third one making the same reply...
Richard was providing a solution to handle the case of a meta redirect
after a metaredirect. He indicates making a redirect (server side would
be the interpretation) to remove the meta redirect flag in the meta
redirects URL. However, it's still flawed since upon a server side
redirect the script would think a manual refresh had occurred :)
However, it can be done embedding an ID in the URL indicating that a
serverside redirect has occurred, then saving that value to a database
so upon a manual refresh that ID is detected as having been used already
and so the manual redirect is detected. Yes, yes, this is kludgy
indeed :)
Cheers,
Rob.
--
...........................................................
SwarmBuy.com - http://www.swarmbuy.com
Leveraging the buying power of the masses!
...........................................................