Robert Erbaron wrote:
yes - abusing redirects as described is wasteful. and certainly it's
the first time I've ever heard the statement 'Never show pages in
response to POST' sounds like hubris too me.
I've seen the statement in a number of messages in the archives here
and in google
Per Jessen schreef:
Robert Erbaron wrote:
yes - abusing redirects as described is wasteful. and certainly it's
the first time I've ever heard the statement 'Never show pages in
response to POST' sounds like hubris too me.
I've seen the statement in a number of messages in the archives here
On Sun, December 16, 2007 2:05 pm, Robert Erbaron wrote:
- Never show pages in response to POST
- Navigate from POST to GET using REDIRECT
- Always load pages using GET
I believe #3 is simply a more general way of saying #1 + #2, but may
be wrong.
And I basically completely disagree with the
And I basically completely disagree with the author in the first
place, so...
Well, that's been clear for a year. :)
(P.S. I'll get to the issue of rearchitecting this via require instead
of using header() redirects,cough, cough, Richard Lynch, cough, cough
:) in a future message. One
I've been reading up on login mechanisms using redirects, and have a
basic mechanism down.
a1.php:
?php
$site_title='My Site';
if (isset($_SESSION['errmsg_s']))
{$errmsg = 'Warning! '.$_SESSION['errmsg_s'].'!';}
else
{$errmsg = ''; }
if (isset($_SESSION['email_s']))
{
Robert Erbaron wrote:
I've been reading up on login mechanisms using redirects, and have a
basic mechanism down.
a1.php:
?php
$site_title='My Site';
if (isset($_SESSION['errmsg_s']))
{$errmsg = 'Warning! '.$_SESSION['errmsg_s'].'!';}
else
{$errmsg = ''; }
if
a standard HTTP request is a GET request.
I guess I'm just missing some basic definition of terminology. Been
writing desktop systems for too long, 'spose.
using firefox and one of a number of extensions (firebug springs to mind)
you can actually view the request headers that are sent.
7 matches
Mail list logo
