While code is planned to run under register_globals=off, it could also be interested to differenciate POST (which implies changes on the server) and GET (which implies no changes will be made). Browsers support POST well and warn the user that data will be reposted when (s)he clicks on 'Back'. I remember having a comment posted twice in a support request after using my browser's history. Handling GET and POST well would avoid that issue. However, I am not sure how I managed to have my comment posted twice, since posting a comment requires using a FORM with the POST method...

--
Sylvain


Stephane URBANOVSKI wrote:
Mathieu Roy wrote:
>
It would make sense to me to write :

if ($_POST['blabla'])
   { $blabla = $_POST['blabla']; }
elseif ($_GET['blabla'])
   { $blabla = $_GET['blabla']; }
   if ($blabla)
   {

   }


or
$blabla = $_REQUEST['blabla'] ;

if ($blabla)
   {

   }

Reply via email to