|
|
Posted by -Lost on 03/29/07 17:36
"Steve" <no.one@example.com> wrote in message news:HiROh.25$Ai4.11@newsfe06.lga...
>| Placing meta information at the bottom? Before the BODY I imagine? Is
> that valid?
>
> 'valid' only applies to browsers that are 100% w3c compliant. as NONE exist,
> the better question is always, 'will it make my browser explode?' we're not
> going to kill anything here. but, we will be getting the desired result.
>
> put the first meta in the head like a good boi. put the next meta just
> before </html>.
>
> | > microsoft had
> | > a whole long write-up on that one b/c their own browser didn't behave as
> web
> | > designers thought it should - they of course offered their explanation
> of
> | > why things were/are the way they were/are...but, at least they gave that
> as
> | > a plausible solution.
> |
> | Thanks. Does that write-up exist still, or no?
>
> sure does...now google. ;^)
>
> | > btw, how do you KNOW ff is caching?
> |
> | It continuously takes a refresh or two (of the form page) before I get my
> POST'd results
> | to display the updated value. I figure it had to be Firefox as the PHP
> context simply
> | dumps the contents of $_POST. If my variable was continually in error, it
> must have been
> | Firefox sending it right?
>
> well, that depends (answered much like a good lawyer). without code, it is
> hard to tell you anything. however, i can most assuredly tell you that
> submitting a form is a one-time deal. the browser sends the data to php...so
> THAT has NOTHING to do with ff caching anything. refreshing the page after
> the first submit only results in that same data being posted to php again
> through the same vehicle/mechanisms as were in play for the first submit.
The code is thus:
if($_POST)
{
foreach($_POST as $index => $value)
{
print $index . ' : ' . $value . '<br />' . "\n";
}
}
That is it.
At one point I did however set a Cache-Control and Expires header in the script first.
> from your description, the problem is with your code...not your browser.
See above.
> | Or some combination of me not setting the correct headers, assuming there
> are any that
> | will make a difference.
> |
> | http://us3.php.net/manual/en/function.header.php#72652
> |
> | Led me to believe it might actually be an Apache issue. I did however try
> using
> | MultiViews as "guesswho" suggested to no avail. I am not familiar with
> any other content
> | negotiation mechanisms of Apache.
>
> always, always, always start debugging from simple to complex. accusing
> apache right off the bat is almost obscene. assume first, that YOU are in
> error and that that error is cause by the most SIMPLE thing. that approach
> will save you copious volumes of time in development hours.
Duly noted.
-Lost
Navigation:
[Reply to this message]
|