|
|
Posted by kenoli on 05/24/07 12:10
Yes, a very clear explanation.
On May 23, 6:25 am, "Steve Belanger" <desk...@ebinformatique.com>
wrote:
> all super globals by default are being set to empty, like $_GET, $_POST,
> $_COOKIE and so on.
>
> you might want to use empty($_POST) instead. If that check ends up being
> true, that means no POST data has been provided. False would mean you sent
> data through $_POST.
>
> hope this helps.
>
> "kenoli" <kenol...@gmail.com> wrote in message
>
> news:1179272305.382461.25810@p77g2000hsh.googlegroups.com...
>
> >I have a script that submits form data via a "post" method to another
> > script. I have an href link in the destination script that links back
> > to itself for processing form data on that page with some "get" data
> > appended to the URL. I noticed that after clicking on that link and
> > sending the action back to itself, a check of isset($_POST) returns
> > true while displaying the content of $_POST displays an empty array.
> > I had expected isset($_POST) to return false, thinking the script
> > would unset the $_POST array when the <a> link sent it back to
> > itself. Instead, it leaves $_POST set but empty.
>
> > What is the convention here?
>
> > --Kenoli
Navigation:
[Reply to this message]
|