Two different POST actions? Possible?

[axlq]

How do I create a form that two submit buttons, where each one
submits the form input data to a different server?

Consider this situation: I have a form where users can check various
options to subscribe to a service, and each option costs a certain
amount. When the form is submitted, my php script totals up the
options. Fine.

The form has 2 submit buttons: "print invoice" and "pay by credit
card."

The "print invoice" button is for those businesses who can't pay by
credit card but must mail us a check instead; they print an invoice
for their accounts payable department. The php script generates the
invoice based on the form inputs. Easy, no problem.

The problem is "pay by credit card." The total cost from submitted
input fields must be POSTed to a different server: our credit card
processor.

This isn't a problem if the credit card processor accepts the
form input data as a GET string in the URL; all I'd do is
header("Locatio n: $url"); to redirect the user to the credit card
processor page which handles the payment. The problem is I need
to do this by POSTing the form input data, while at the same time
retain the ability to generate invoices from MY server using the
same form.

I can't think of an elegant way to do this except to have two
different payment pages each with their own form. Or maybe force
everybody to generate an invoice as the first step, and after that
point they can choose to pay it by credit card.

-A

[pengypenguin]

What I did was to create a dummy action in the post form, and use a
javascript function to swap in a new action and then call the submit
method based on the onclick of different buttons.

-- whit

axlq wrote:

How do I create a form that two submit buttons, where each one
submits the form input data to a different server?

Consider this situation: I have a form where users can check various
options to subscribe to a service, and each option costs a certain
amount. When the form is submitted, my php script totals up the
options. Fine.

The form has 2 submit buttons: "print invoice" and "pay by credit
card."

The "print invoice" button is for those businesses who can't pay by
credit card but must mail us a check instead; they print an invoice
for their accounts payable department. The php script generates the
invoice based on the form inputs. Easy, no problem.

The problem is "pay by credit card." The total cost from submitted
input fields must be POSTed to a different server: our credit card
processor.

This isn't a problem if the credit card processor accepts the
form input data as a GET string in the URL; all I'd do is
header("Locatio n: $url"); to redirect the user to the credit card
processor page which handles the payment. The problem is I need
to do this by POSTing the form input data, while at the same time
retain the ability to generate invoices from MY server using the
same form.

I can't think of an elegant way to do this except to have two
different payment pages each with their own form. Or maybe force
everybody to generate an invoice as the first step, and after that
point they can choose to pay it by credit card.

-A

[Andrew Poelstra]

pe**********@gm ail.com writes:

axlq wrote:

>How do I create a form that two submit buttons, where each one
submits the form input data to a different server?

Consider this situation: I have a form where users can check various
options to subscribe to a service, and each option costs a certain
amount. When the form is submitted, my php script totals up the
options. Fine.

The form has 2 submit buttons: "print invoice" and "pay by credit
card."

The "print invoice" button is for those businesses who can't pay by
credit card but must mail us a check instead; they print an invoice
for their accounts payable department. The php script generates the
invoice based on the form inputs. Easy, no problem.

The problem is "pay by credit card." The total cost from submitted
input fields must be POSTed to a different server: our credit card
processor.

This isn't a problem if the credit card processor accepts the
form input data as a GET string in the URL; all I'd do is
header("Locati on: $url"); to redirect the user to the credit card
processor page which handles the payment. The problem is I need
to do this by POSTing the form input data, while at the same time
retain the ability to generate invoices from MY server using the
same form.

I can't think of an elegant way to do this except to have two
different payment pages each with their own form. Or maybe force
everybody to generate an invoice as the first step, and after that
point they can choose to pay it by credit card.

What I did was to create a dummy action in the post form, and use a
javascript function to swap in a new action and then call the submit
method based on the onclick of different buttons.

Please don't top-post. I've corrected it above.

Also, Javascripting a critical part of a website is always a Bad
Idea. Many people, such as myself, have browsers that don't support
Javascript. Many people disable Javascript in their browsers to
avoid popups, ads, etc.

A better solution to this would be to create a confirmation page
for the credit card purchase which has an additional submit button
that goes only to the credit card company.

The confirmation page can be the invoice page, except that it checks
which button was clicked and either displays an invoice or a
confirmation (or both).

--
Andrew Poelstra <http://www.wpsoftware. net/projects>
To reach me by email, use `apoelstra' at the above domain.
"Do BOTH ends of the cable need to be plugged in?" -Anon.

[axlq]

In article <11************ **********@h48g 2000cwc.googleg roups.com>,
<pe**********@g mail.comwrote:

>What I did was to create a dummy action in the post form, and use a
javascript function to swap in a new action and then call the submit
method based on the onclick of different buttons.

I prefer not to rely on javascript for something this critical.
Javascript is fine for user convieniences such as form data
validation and expandable list trees, but the web site should
still function properly without it. A Lynx user should be able to
navigate through the form.

Using the invoice as a confirmation page before credit card purchase
seems like the best approach. Not what I want exactly, but it will
work.

-A

[Alvaro G. Vicario]

*** Andrew Poelstra escribió/wrote (Fri, 25 Aug 2006 14:25:01 GMT):

Many people disable Javascript in their browsers

Many developers love to think that users do so, but they don't :)

But of course JavaScript is the worst tool for critical tasks. Among many
other reasons, because developers who abuse JavaScript tend to be terrible
coders and their scripts fail in browsers that are not Internet Explorer
(and pretty often in IE itself). Good JavaScript coders just leave
scripting for auxiliary tasks.
--
-+ http://alvaro.es - Álvaro G. Vicario - Burgos, Spain
++ Mi sitio sobre programación web: http://bits.demogracia.com
+- Mi web de humor con rayos UVA: http://www.demogracia.com
--

[NC]

axlq wrote:

>
How do I create a form that two submit buttons, where each one
submits the form input data to a different server?

You can't. Just separate the forms. Like this:

<table>
<tr>
<td><form method="POST"
action="http://www.yoursite.co m/path/printinvoice.ph p">
<input type="hidden" name="custid" value="Customer _ID">
<input type="hidden" name="date" value="Date_of_ Invoice">
<!-- more fields if necessary -->
<input type="submit" value="Print Invoice">
</form>
<td>form method="POST"
action="https://www.yourpayment processor.com/path/">
<input type="hidden" name="merchantI D" value="Your_Mer chant__ID">
<input type="hidden" name="amount" value="Amount_o f_Payment">
<!-- more fields if necessary -->
<input type="submit" value="Pay by Credit Card">
</form>
</table>

The invoice printing script and the payment gateway are likely to
require different sets of data anyway...

Or maybe force everybody to generate an invoice as
the first step, and after that point they can choose to
pay it by credit card.

Not a bad idea, either.

Cheers,
NC

[Andrew Poelstra]

"Alvaro G. Vicario" <we*******@NOSP AMdemogracia.co mwrites:

*** Andrew Poelstra escribió/wrote (Fri, 25 Aug 2006 14:25:01 GMT):

>Many people disable Javascript in their browsers

Many developers love to think that users do so, but they don't :)

Okay, I'll bite. I'm a user and I use lynx. I also disable Javascript in
all my GUI-browsers so that I don't have to see popups and other crap.

Of course, you may argue that as a developer I don't count as a "user".
:-)

But of course JavaScript is the worst tool for critical tasks. Among many
other reasons, because developers who abuse JavaScript tend to be terrible
coders and their scripts fail in browsers that are not Internet Explorer
(and pretty often in IE itself). Good JavaScript coders just leave
scripting for auxiliary tasks.

That's definitely true; I have a grammar checker written in Javascript
(no, it doesn't work well enough for me to link to it here), and it takes
several seconds to parse only a few kilobytes of text. I have no idea what
it'd do if transferred to IE (there's virtually no IO, so I'd assume that
it would be fine).

Whereas the logic, if transferred to C, would run through thousands of
times that much text in as little time. On a processor only 10% as
powerful.

--
Andrew Poelstra <http://www.wpsoftware. net/projects>
To reach me by email, use `apoelstra' at the above domain.
"Do BOTH ends of the cable need to be plugged in?" -Anon.

[axlq]

In article <11************ *********@b28g2 000cwb.googlegr oups.com>,
NC <[e-mail] ote:

>axlq wrote:

>How do I create a form that two submit buttons, where each one
submits the form input data to a different server?

You can't. Just separate the forms. Like this:

[snip]

Then I have redundant fields that need to be filled in twice. That's
exactly what I was trying to avoid. I wanted one form with two
submit buttons, each sending the data to a separate server.

>The invoice printing script and the payment gateway are likely to
require different sets of data anyway...

Why? I just use the payment gateway POST data to generate the
invoice.

>Or maybe force everybody to generate an invoice as
the first step, and after that point they can choose to
pay it by credit card.

Not a bad idea, either.

Based on the responses, it looks like that's the way to go.

-Alex

[NC]

axlq wrote:

>

The invoice printing script and the payment gateway are
likely to require different sets of data anyway...

Why? I just use the payment gateway POST data to generate
the invoice.

Why would you ever do that? You are giving away your (or your
customer's) internal information, which the payment processor is under
no obligation to safeguard. The only information you should give the
payment processor is that which is required to process payment (credit
card information and the amount). The rest (items and quantities)
should be kept internal.

Cheers,
NC

[jussist]

Many developers love to think that users do so, but they don't :)

Of course, you may argue that as a developer I don't count as a "user".
:-)

Both of these are very true. I used to work for a government office in
Finland. There was about 2500 employees. If I remember correctly, in IE
javascript was disabled as default. And stayed that way for most users,
naturally.