#SusanP - Checkout Page

1 messages ยท Page 1 of 1 (latest)

winged sequoia
#

Hi ๐Ÿ‘‹
I'm unclear what you mean here. The checkout page is a Stripe hosted solution that is navigated to via a standard GET request but does submit it's form via a POST request. But this should not have an impact on your integration.

Are you referring to the redirection to the success_url?

raw dock
#

No, sorry, I am referring to the URL that I generate for the checkout session and then I redirect to. If I POST to it instead of issuing a redirect header, it fails. Any way around that?

winged sequoia
#

No, POST requests are not used for normal navigation. POST requests should only be used for requests that change data.

raw dock
#

yeah i know. it's something I don't have easy control over. I figured you wouldn't support it but I had to ask! Thanks ๐Ÿ™‚

winged sequoia
#

Sure thing.

#

So you're not coding this yourself? Or you cannot just add the checkout.url to a button or something?

raw dock
#

I'm coding it myself but it's within the context of the Miva Merchant shopping cart. I can return the generated URL from a function, but by default that function goes in as the "action" of a form element whose "method" is POST. It can be changed, but it would require any retailer using the module to change their template code. I can't just change the form method in the module itself.

#

and in my experience, having retailers change template code isn't the best idea if it can be avoided

winged sequoia
#

Redirecting through a <form> action seems odd to me. Like that should set some data somewhere and then redirect in response to the POST request. But I fully admit I am not familiar with this particular tech.

raw dock
#

Normally that screen would present a form, such as credit card number and expiration date fields. But it can also just be a passthrough, such as it does with Paypal. But PayPal's URL doesn't block POST requests, so that one works fine.

winged sequoia
#

Okay. I did some digging and I cannot find anyone mentioning it as an issue to be addressed. I guess this is a rare use case

raw dock
#

i think so too. overall my integration works, though, so I think my client will just have to live with needing to change the template code. Thank you for looking for me and talking through it! Have a great day.