Apache/PHP Post Variables

[Tony]

I'm working with someone on a PHP project. The other person is doing
testing of scripts on their personal machine using Apache as a web server.
The production server and the one I'm using are both using IIS.

This other person reports that in their PHP scripts when tested with Apache,
form variable sent via the POST method are not "coming through." (This is
even using the "long method" of specifying them as $HTTP_POST_VARS['x'].)
These same scripts work fine on the the IIS machine (the POST variable come
through).

I've looked online to see if I can find out if anything special must be
specified in the Apache configuration to enable the POST method, and
although I found other people posting similar problems, I saw no reference
to a solution.

Can anyone tell me what must be done to get this to work as it should with
Apache?

Thanks.

Tony

[steven mestdagh]

In comp.lang.php Tony <no****@pittarese.com> wrote:

This other person reports that in their PHP scripts when tested with Apache,
form variable sent via the POST method are not "coming through." (This is
even using the "long method" of specifying them as $HTTP_POST_VARS['x'].)
These same scripts work fine on the the IIS machine (the POST variable come
through).

probably there is nothing wrong with your apache setup.
try $_POST['x'] instead of $HTTP_POST_VARS['x'] .
$_POST is a superglobal array, whereas $HTTP_POST_VARS is not.
for more information, see
http://www.php.net/reserved.variables

if this doesn't solve your problem...
which version of PHP are you using? have you inspected the apache log
files for errors?

regards,
steven.

[Joshua Beall]

"steven mestdagh" <st*************@esat.kuleuven.REMOVE-THIS.ac.be> wrote in
message news:10***************@seven.kulnet.kuleuven.ac.be ...

In comp.lang.php Tony <no****@pittarese.com> wrote:

This other person reports that in their PHP scripts when tested with Apache, form variable sent via the POST method are not "coming through." (This is even using the "long method" of specifying them as $HTTP_POST_VARS['x'].) These same scripts work fine on the the IIS machine (the POST variable come through).

probably there is nothing wrong with your apache setup.
try $_POST['x'] instead of $HTTP_POST_VARS['x'] .
$_POST is a superglobal array, whereas $HTTP_POST_VARS is not.

I would also suggest print_r($GLOBALS), and see if that reveals anything
interesting.

[Dan Tripp]

Joshua Beall wrote:

"steven mestdagh" <st*************@esat.kuleuven.REMOVE-THIS.ac.be> wrote in
message news:10***************@seven.kulnet.kuleuven.ac.be ...

In comp.lang.php Tony <no****@pittarese.com> wrote:

This other person reports that in their PHP scripts when tested with
Apache,
form variable sent via the POST method are not "coming through." (This
is
even using the "long method" of specifying them as
$HTTP_POST_VARS['x'].)
These same scripts work fine on the the IIS machine (the POST variable
come
through).

probably there is nothing wrong with your apache setup.
try $_POST['x'] instead of $HTTP_POST_VARS['x'] .
$_POST is a superglobal array, whereas $HTTP_POST_VARS is not.

I would also suggest print_r($GLOBALS), and see if that reveals anything
interesting.

This sounds like a register_globals problem. Check the PHP.ini file on
the dev machine, and it'll probably show register_globals = off.

Before you change it to "on" however, take a look at:
http://www.php.net/register_globals

I'd go so far as to recommend that your two IIS boxes should probably
have register_globals turned off.

Regards,

- Dan
http://blog.dantripp.com/

[Tony]

"Dan Tripp" <th*******@MyEMailAddress.com> wrote in message news:_oOXb.25623

This sounds like a register_globals problem. Check the PHP.ini file on
the dev machine, and it'll probably show register_globals = off.

Before you change it to "on" however, take a look at:
http://www.php.net/register_globals

Thanks to all those who posted info. Prior to running into this problem I
wasn't well informed about the issues related to the globals. I appreciate
the replies.

Unfortunately, the book I've been using as my primary reference (PHP and
MySQL Web Development by Welling and Thomson) uses $HTTP_POST_VARS in
examples and doesn't explain why this might be a bad thing. (That's 1 of
about 5 problems or errors I've found in my use of this book so far.)

Thanks for all the great info provided.

Tony

[Phillip Parr]

I just use the $_REQUEST['variable'] thingy for forms, works for me!
"Tony" <no****@pittarese.com> wrote in message
news:c0********@library2.airnews.net...

"Dan Tripp" <th*******@MyEMailAddress.com> wrote in message news:_oOXb.25623

This sounds like a register_globals problem. Check the PHP.ini file on
the dev machine, and it'll probably show register_globals = off.

Before you change it to "on" however, take a look at:
http://www.php.net/register_globals

Thanks to all those who posted info. Prior to running into this problem I
wasn't well informed about the issues related to the globals. I

appreciate the replies.

Unfortunately, the book I've been using as my primary reference (PHP and
MySQL Web Development by Welling and Thomson) uses $HTTP_POST_VARS in
examples and doesn't explain why this might be a bad thing. (That's 1 of
about 5 problems or errors I've found in my use of this book so far.)

Thanks for all the great info provided.

Tony

[Eric Bohlman]

"Phillip Parr" <no****@here.com> wrote in
news:jx******************@news-binary.blueyonder.co.uk:

I just use the $_REQUEST['variable'] thingy for forms, works for me!

The problem with $_REQUEST is that what goes into it is determined by
php.ini settings, so it can create portability problems. Also, depending
on those settings, cookie names and environment-variable names wind up
sharing the same namespace as GET and POST parameter names, and may in fact
overwrite them. So it's really appropriate only when you have complete
control over the environment in which PHP is running and don't expect the
code to be moved to any other environment.

[Joshua Beall]

"Eric Bohlman" <eb******@earthlink.net> wrote in message
news:Xn*******************************@130.133.1.4 ...

"Phillip Parr" <no****@here.com> wrote in
news:jx******************@news-binary.blueyonder.co.uk:
The problem with $_REQUEST is...

<snip>

Let me summarize for you: Do not use $_REQUEST. It is bad idea. Use $_GET,
$_POST, or $_COOKIE.

;-)

-jb

[Phillip Parr]

Ok then. You spoilin all my fun!

"Joshua Beall" <jb****@donotspam.remove.me.heraldic.us> wrote in message
news:5I*******************@nwrddc01.gnilink.net...

"Eric Bohlman" <eb******@earthlink.net> wrote in message
news:Xn*******************************@130.133.1.4 ...

"Phillip Parr" <no****@here.com> wrote in
news:jx******************@news-binary.blueyonder.co.uk:
The problem with $_REQUEST is... <snip>

Let me summarize for you: Do not use $_REQUEST. It is bad idea. Use

$_GET, $_POST, or $_COOKIE.

;-)

-jb