Re: Is there a way to distinguish an auto-refresh from a manual page load? [message #177209 is a reply to message #177208] |
Mon, 27 February 2012 16:18 |
alvaro.NOSPAMTHANX
Messages: 277 Registered: September 2010
Karma:
|
Senior Member |
|
|
El 27/02/2012 15:12, The Natural Philosopher escribió/wrote:
>>> Well that is the problem isn't it? The browser cannot KNOW. If I POST a
>>> form to mypostingtarget.php and THAT comes back with a 'meta refresh'
>>> statement THAT is the target that is going to be refreshed?.
>>
>> Okay, I think I finally see what the problem is.
>>
>> The complete syntax for a <meta> direct is this:
>>
>> https://developer.mozilla.org/en/HTML/Element/meta#attr-http-equiv
>>
>> In the "refresh" bit we can read:
>>
>> «This pragma specifies:
>>
>> - the number of seconds until the page should be reloaded, if the
>> content attribute contains only a positive integer number;
>>
>> - the number of seconds until the page should be redirected to
>> another, if the content attribute contains a positive integer number
>> followed by the string ';url=' and a valid URL.»
>>
>> I guess you are using the first feature ("reload") and I thought you
>> were using the second one ("redirect"). Just tweak your PHP code to
>> generate a <meta> tag with the ";url=" part.
>>
>>
>
> Oh, so what you are saying is that a POST operation generates a page
> that has a redirect back to the page that produced the POST *request*
> not the *result*, but then that *is* the page that if refreshed again
> will POST again.. ;-0)
I'm just saying that:
1. A redirect always triggers a GET request.
2. It's _your_ page and _you_ control what URL is written into the
<meta> tag.
Honestly, I'm completely lost as about what's not clear so far.
--
-- http://alvaro.es - Álvaro G. Vicario - Burgos, Spain
-- Mi sitio sobre programación web: http://borrame.com
-- Mi web de humor satinado: http://www.demogracia.com
--
|
|
|