The SitePoint Forums have moved.

You can now find them here.
This forum is now closed to new posts, but you can browse existing content.
You can find out more information about the move and how to open a new account (if necessary) here.
If you get stuck you can get support by emailing forums@sitepoint.com

If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

in environment one, there is no echo content type (no required). however, if i enter test@test.com for "data['value']" it comes back with "@test.com". seems to arbitrarily butcher various inputs as well

in environment two and three, nothing comes back (no get or post)

any ideas? i'm about to age 50 years and lose all my hair... found the following:

Firstly, PHP is not perl: it doesn't require you to explicitly send the content-type header.
Secondly, unless the server is very badly configured you shouldn't require the shebang line either.
Thirdly, PHP will only execute scripts with the extension "php" unless the server is explicitly told to treat other files as PHP.

hey thanks for the suggestions thus far, i might need to clarify. i'm running it as a cgi (ie, like perl or python without mod_perl/python) and due to the setup it will need to be with the shebang, etc...

the current deployment environment is php 4.2.3 (cgi) whereas it will be upgraded shortly to php 4.3.4 (cli).

as far as i'm aware, the CLI version does require the echo content-type (would be glad to be proved wrong on this ).

based on that, $_GET and $_POST should be setup as normal should they not?

this is essentially a basic pass variables from one page in the cgi-bin to another but using php, and i'm baffled as to why it's giving me so many problems.

hey cool, i semi solved my issue. as noted, cli / cgi are quite different thing, for some reason my little brain couldn't grasp that concept. i'm just going to use a stripped down php binary for this project, it'll work like a charm, and won't need to worry about the main php binary being upgraded.