On Wed, Dec 1, 2010 at 12:15, Nadim Attari <nadim@xxxxxxxxxxxxxxxx> wrote:
>
> where does receipt.php gets the $_GET data ? Isn't it from response.php
> where the $_POST data are being http_build_query()'ed ??
>
> $param = http_build_query($_POST); <---------
According to cURL, it's never even hitting response.php to
redirect. It's going straight to receipt.php with $_GET data. (THERE
IS NO $_POST DATA.)
Besides, you kept stating that the 'redirect' was working fine,
which is technically incorrect: there's absolutely zero chance that
works as you presented it. You can't just throw in some text to tell
the browser to redirect to a page. You'd have to do a
header("Location: "); call, a meta refresh, a JavaScript
window.location() call or something similar. Thus that indicates that
the text from response.php is interpreted as a direction by the
processing gateway's API when it calls out to your server.
Knowing this, I see the $_POST data expected here. This wasn't in
question, as it's obviously building the query string. We now know
that it feeds this data in plain text back to the remote server for
further processing, which then directs the browser to receipt.php ---
with $_GET data (id est - THERE IS NO $_POST DATA).
Your browser is never hitting response.php. Only the remote
server is doing that. If you want to get the data as sent by the
remote server to your server in response.php, you'll either need to
write that to a file like I did:
file_put_contents('output.nadim.log',$param);
Or you'll need to consult the processing gateway's API
documentation to learn how to avoid requiring this seemingly
unnecessary step.
--
</Daniel P. Brown>
Dedicated Servers, Cloud and Cloud Hybrid Solutions, VPS, Hosting
(866-) 725-4321
http://www.parasane.net/
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
