$_POST not always set?

On 30 Apr 2004 00:27:22 GMT
Pedro Graca <hexkid@hotpop.com> wrote:

> Kelly Thompson wrote:
> > On 29 Apr 2004 23:05:36 GMT
> > Eric Bohlman <ebohlman@earthlink.net> wrote:
> >
> >> Pedro Graca <hexkid@hotpop.com> wrote in news:c6rtun$fklfl$1@ID-
> >> 203069.news.uni-berlin.de:
> >>
> >> > Or use the $_REQUEST array, which inludes $_GET, $_POST, and
> >> > $_COOKIE :)
> >>
> >> That depends on a setting in php.ini, so I wouldn't recommend it
> >to> newbies or to anyone who doesn't have complete control over
> >their> server. Using it mindlessly can result in code that
> >mysteriously> breaks when moved to another system.
>
> Thank you for pointing that out, Eric.
>
> > Which setting?
>
> gpc_order
>
> In my php.ini it is
>
> gpc_order = "GPC"
>
> so if there is a $_GET['x'], a $_POST['x'], and a $_CCOKIE['x']
> on my configuration $_REQUEST['x'] will be $_COOKIE['x']

Then one more reason to do it yourself with array_merge().

I often run into situations where there is nothing stored in $_POST.
For me, whenever I run into this, it turns out that the version of PHP
on the server I'm on is pre- version 4.1.