Posting without a submit - automatically

Anon

I would like to submit hidden variables from one program to another and have the values be sent on as an email, but at the same time, have those values be posted to an new program that is run from the email program.

For example:

Form program ----> Click on submit. Posts to a new program

New program sends out an email then ----> runs a new program automatically with the same values as the hidden ones from the first form program.

Or can 2 posts be done from one program from the same submit button using the hidden fields?

Any ideas would be appreciated.

Thanks...
Philip

Anon

Why not have your 3rd(?) script do the emailing as it's first action, instead of having a separate email script in between.

You could still have a separate script and just call it from your 3rd(?) script and pass the variables as a get to it, but not have it output anything to the screen.

Anon

Or another trick might be to include some javascript. While one page can't POST to two pages at once, the first page could could POST to the 2nd page which then POSTs to the third page automatically via a bit of javascript. Include a button to continue for those that either don't have javascript or have chosen to disable it.

example (i haven't tested it):

/ submit form /

/ email page (send.php) /

<BODY>
Sending the Email.
<?
#some php function to do the real work
sendmessage($text_name);
?>

</BODY>

/ success/fail page (results.php) /

<BODY>
test_name: <? echo $test_name; ?>
<BR>Success!
</BODY>

Anon

A fun little trick is the use of fopen().

For instance, the following url:

www.dot.com/login.php?name=bob&pass=63fT

If your script examined the name and pass variables to authenticate the user, and the user simply pasted this url into his browser, as long as the values were correct your script would log your user in.

Your script wouldn't even know the user never clicked the "submit" button.

Now, the fun part.

If you use fopen() to call that url from your own script, the targeted script will think bob hit the submit button and wanted to log in.

Thus you can "automatically" log bob in, using your own PHP script.

Now, the key here is to take the data your user entered into your script, replicate it into a full url (the url of your 2nd script), and we'll call that value $url.

When your user clicks submit, the script targeted will accept the data, activate mail(), create $url, then use fopen("$url", "r") which is exactly the same as had the orginal "submit" script been targeted to your 3rd script.

I have absolutely endless amounts of fun with this little feature 🙂

If I explained it in a confusing way, just say so and I'll try doing it in a different way 🙂

bbbear

Good day Plutarck,

I was searching for ways to automatically runs a script at the backend and I've tested with your way. However, I have not manage to get my script run, so, thought to consult you.

Let me give you a clearer picture of what I want to do. Assume I have a script named post.php where it'll receive some variables from a form. After some verifications, "post.php" will invoke a script named "test.php" from another server. "test.php" will write the data where it received from the form into a file. I've managed to succeed in calling the fopen function but not with creating the new files. Here's my script:

post.php:
<?
......
......

    $url = "http://192.xxx.xxx.xxx/~path/to/project/test.php?login=$login&var=$var";

    print $x = fopen("$url", "r");
    print "<br>";

    if($x)
            print "The script file exist!<br>";
    else
            print "The script file doesn't exist!<br>";

test.php:
<?
srand((double)microtime()*1000000);
$filename = rand();
$ar_var[0] = $login;
$ar_var[1] = $var;
$str = join($ar_var, ";");

    $fp = fopen($filename, "w");
    //$chmodfile = `chmod 777 $file`;
    fwrite($fp, $str, strlen($str));
    fclose($fp);

Have I missed anything ?

Thanks in advance for your help.

Anon

Which part of the script is failing?

One problem may simply be that the permissions you have set are allowing the file to be written to.

In UNIX you will probably need to allow WRITE access for the entire directory you put the files in. Obviously unsafe in some cases, but not being able to create/write to the file is probably your problem.