Post with redirect?

Quote:

Quote:

Quote:

Quote:

Quote:

Quote:

Quote:

Quote:

Quote:

Quote:

Hi,

I'm not sure if this can be done as I've searched the web and this
forum.

I am using an online merchant provider and I must post certain
variables to their webforms through a form on my website.

The issue is that I need to gauge whether a user has any items in
their basket to decide which page I redirect them too. I could
obviously use cookies or hidden fields etc but these can be
manipulated.

How can I force a POST but actually redirect the user as well like a
browser would do? I can do the first part (force the post) as per this
site (the site appears down, so the link uses the Web Archive):
>http://web.archive.org/web/200406282...nd.com/zend/sp...

Its the second bit if I'm not sure whether it can or can't be done.

If not I'll need to ask the merchant if they allow GET instead.

Many thanks

A

Quote:

On 14 Dec, 12:48, Jerry Stuckle <jstuck...@attglobal.netwrote:
>UKuser wrote:
Hi,

I'm not sure if this can be done as I've searched the web and this
forum.

I am using an online merchant provider and I must post certain
variables to their webforms through a form on my website.

The issue is that I need to gauge whether a user has any items in
their basket to decide which page I redirect them too. I could
obviously use cookies or hidden fields etc but these can be
manipulated.

How can I force a POST but actually redirect the user as well like a
browser would do? I can do the first part (force the post) as per
this
site (the site appears down, so the link uses the Web Archive):
>http://web.archive.org/web/200406282...nd.com/zend/sp...

Its the second bit if I'm not sure whether it can or can't be done.

If not I'll need to ask the merchant if they allow GET instead.

Many thanks

A

>Not easy, and it can't be done with PHP. The browser needs to process
>the redirect, so you need to do it from the browser end. That means a
>client-side language such as javascript.

>cURL could theoretically help you here - but you're asking for a lot
>of
>work, especially if there are several pages being handled after the
>redirect. You'd have to parse each page to see what to do next.

>--
>==================
>Remove the "x" from my email address
>Jerry Stuckle
>JDS Computer Training Corp.
>jstuck...@attglobal.net
>==================

Thanks for your help. Should have realised because its server side it
makes it impossible. Any thoughts on how it could be done with AJAX/JS?

Quote:

"UKuser" <spiderc...@yahoo.co.ukwrote in message

Quote:

>news:6d60314f-61f0-4f08-b1ad-b6cf357cac15@a35g2000prf.googlegroups.com...

Quote:

On 14 Dec, 12:48, Jerry Stuckle <jstuck...@attglobal.netwrote:
UKuser wrote:
Hi,

Quote:

I'm not sure if this can be done as I've searched the web and this
forum.

Quote:

I am using an online merchant provider and I must post certain
variables to their webforms through a form on my website.

Quote:

The issue is that I need to gauge whether a user has any items in
their basket to decide which page I redirect them too. I could
obviously use cookies or hidden fields etc but these can be
manipulated.

Quote:

How can I force a POST but actually redirect the user as well like a
browser would do? I can do the first part (force the post) as per
this
site (the site appears down, so the link uses the Web Archive):
http://web.archive.org/web/200406282...nd.com/zend/sp...

Quote:

Its the second bit if I'm not sure whether it can or can't be done.

Quote:

If not I'll need to ask the merchant if they allow GET instead.

Quote:

Many thanks

Quote:

A

Quote:

Not easy, and it can't be done with PHP. The browser needs to process
the redirect, so you need to do it from the browser end. That means a
client-side language such as javascript.

Quote:

cURL could theoretically help you here - but you're asking for a lot
of
work, especially if there are several pages being handled after the
redirect. You'd have to parse each page to see what to do next.

Quote:

--
==================
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
jstuck...@attglobal.net
==================

Quote:

Thanks for your help. Should have realised because its server side it
makes it impossible. Any thoughts on how it could be done with AJAX/JS?

Quote:

don't let the misinformation fool you. it can be done with php. the only
thing jerry got right is that it would be a lot of work. what jerry also
mistakenly forgets is that just about anything you can do with curl, you
can
do with native php functions...and in this case, the 'just about
anything'
you'd need to be able to do becomes 'anything'. jerry's 'curl could
theoretically' argument then logically negates and invalidates his 'cant
be
done with php' claim.

Quote:

you're just in for a lot of work. however, it can be done.

Quote:

Quote:

Quote:

On 14 Dec, 14:42, "Steve" <no....@example.comwrote:
>"UKuser" <spiderc...@yahoo.co.ukwrote in message

>>news:6d60314f-61f0-4f08-b1ad-b6cf357cac15@a35g2000prf.googlegroups.com...

On 14 Dec, 12:48, Jerry Stuckle <jstuck...@attglobal.netwrote:
>UKuser wrote:
Hi,

I'm not sure if this can be done as I've searched the web and
this
forum.

I am using an online merchant provider and I must post certain
variables to their webforms through a form on my website.

The issue is that I need to gauge whether a user has any items in
their basket to decide which page I redirect them too. I could
obviously use cookies or hidden fields etc but these can be
manipulated.

How can I force a POST but actually redirect the user as well
like a
browser would do? I can do the first part (force the post) as per
this
site (the site appears down, so the link uses the Web Archive):
>http://web.archive.org/web/200406282...nd.com/zend/sp...

Its the second bit if I'm not sure whether it can or can't be
done.

If not I'll need to ask the merchant if they allow GET instead.

Many thanks

A

>Not easy, and it can't be done with PHP. The browser needs to
>process
>the redirect, so you need to do it from the browser end. That
>means a
>client-side language such as javascript.

>cURL could theoretically help you here - but you're asking for a
>lot
>of
>work, especially if there are several pages being handled after the
>redirect. You'd have to parse each page to see what to do next.

>--
>==================
>Remove the "x" from my email address
>Jerry Stuckle
>JDS Computer Training Corp.
>jstuck...@attglobal.net
>==================

Thanks for your help. Should have realised because its server side
it
makes it impossible. Any thoughts on how it could be done with
AJAX/JS?

>don't let the misinformation fool you. it can be done with php. the
>only
>thing jerry got right is that it would be a lot of work. what jerry
>also
>mistakenly forgets is that just about anything you can do with curl,
>you
>can
>do with native php functions...and in this case, the 'just about
>anything'
>you'd need to be able to do becomes 'anything'. jerry's 'curl could
>theoretically' argument then logically negates and invalidates his
>'cant
>be
>done with php' claim.

>you're just in for a lot of work. however, it can be done.

Hi Guys,

I'm not greatly up for a huge deal of work although would be
interested in how you would generally start doing it in PHP. However I
found another posting on a forum which works and is much easier. Not
ideal although we are really only (and i know its aweful) aiming our
website at Javascript users.

Quote:

"UKuser" <spiderc...@yahoo.co.ukwrote in message

Quote:

>news:5202d2ed-02a2-407d-87ca-a6a2b50a283c@s8g2000prg.googlegroups.com...

Quote:

On 14 Dec, 14:42, "Steve" <no....@example.comwrote:
"UKuser" <spiderc...@yahoo.co.ukwrote in message

Quote:

>news:6d60314f-61f0-4f08-b1ad-b6cf357cac15@a35g2000prf.googlegroups.com...

Quote:

On 14 Dec, 12:48, Jerry Stuckle <jstuck...@attglobal.netwrote:
UKuser wrote:
Hi,

Quote:

I'm not sure if this can be done as I've searched the web and
this
forum.

Quote:

I am using an online merchant provider and I must post certain
variables to their webforms through a form on my website.

Quote:

The issue is that I need to gauge whether a user has any items in
their basket to decide which page I redirect them too. I could
obviously use cookies or hidden fields etc but these can be
manipulated.

Quote:

How can I force a POST but actually redirect the user as well
like a
browser would do? I can do the first part (force the post) as per
this
site (the site appears down, so the link uses the Web Archive):
http://web.archive.org/web/200406282...nd.com/zend/sp...

Quote:

Its the second bit if I'm not sure whether it can or can't be
done.

Quote:

If not I'll need to ask the merchant if they allow GET instead.

Quote:

Many thanks

Quote:

A

Quote:

Not easy, and it can't be done with PHP. The browser needs to
process
the redirect, so you need to do it from the browser end. That
means a
client-side language such as javascript.

Quote:

cURL could theoretically help you here - but you're asking for a
lot
of
work, especially if there are several pages being handled after the
redirect. You'd have to parse each page to see what to do next.

Quote:

--
==================
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
jstuck...@attglobal.net
==================

Quote:

Thanks for your help. Should have realised because its server side
it
makes it impossible. Any thoughts on how it could be done with
AJAX/JS?

Quote:

don't let the misinformation fool you. it can be done with php. the
only
thing jerry got right is that it would be a lot of work. what jerry
also
mistakenly forgets is that just about anything you can do with curl,
you
can
do with native php functions...and in this case, the 'just about
anything'
you'd need to be able to do becomes 'anything'. jerry's 'curl could
theoretically' argument then logically negates and invalidates his
'cant
be
done with php' claim.

Quote:

you're just in for a lot of work. however, it can be done.

Quote:

Hi Guys,

Quote:

I'm not greatly up for a huge deal of work although would be
interested in how you would generally start doing it in PHP. However I
found another posting on a forum which works and is much easier. Not
ideal although we are really only (and i know its aweful) aiming our
website at Javascript users.

Quote:

as a general and theoretical approach:

Quote:

function getResponse($uri, $path, $data, $method = 'POST')
{
$method = strtoupper($method);
$socket = fsockopen($uri, 80);
if (!$method)){ $method = 'GET'; }
if (substr($path, 0) != '/'){ $path = '/' . $path; }
if (!is_array($data)){ $data = array($data); }
$message = '';
foreach ($data as $label =$value)
{
$message .= '&' . $label . '=' . $value;
}
if ($method == 'GET'){ $path .= '?' . $message; }
fputs($socket, "$method $path http/1.1\r\n");
fputs($socket, "host: $uri\r\n");
fputs($socket, "content-type: application/x-www-form- urlencoded\r\n");
fputs($socket, "content-length: " . strlen($message) . "\r\n");
fputs($socket, "connection: close\r\n\r\n");
if ($method == 'POST'){ fputs($socket, $message); }
while (!feof($socket)){ $response .= fgets($socket, 512); }
fclose($socket);
return $response;

Quote:

}

Quote:

$response = getResponse(
'www.example.com',
'some.page.php' ,
$_POST ,
'POST'
);
// parse, validate, process

Quote:

effectively, this achieves your html/javascript solution and keeps it all
php.

Quote:

that help?

Quote:

Quote:

Quote:

On 14 Dec, 15:18, "Steve" <no....@example.comwrote:
>"UKuser" <spiderc...@yahoo.co.ukwrote in message

>>news:5202d2ed-02a2-407d-87ca-a6a2b50a283c@s8g2000prg.googlegroups.com...

On 14 Dec, 14:42, "Steve" <no....@example.comwrote:
>"UKuser" <spiderc...@yahoo.co.ukwrote in message

>>news:6d60314f-61f0-4f08-b1ad-b6cf357cac15@a35g2000prf.googlegroups.com...

On 14 Dec, 12:48, Jerry Stuckle <jstuck...@attglobal.netwrote:
>UKuser wrote:
Hi,

I'm not sure if this can be done as I've searched the web and
this
forum.

I am using an online merchant provider and I must post certain
variables to their webforms through a form on my website.

The issue is that I need to gauge whether a user has any items
in
their basket to decide which page I redirect them too. I could
obviously use cookies or hidden fields etc but these can be
manipulated.

How can I force a POST but actually redirect the user as well
like a
browser would do? I can do the first part (force the post) as
per
this
site (the site appears down, so the link uses the Web
Archive):
>http://web.archive.org/web/200406282...nd.com/zend/sp...

Its the second bit if I'm not sure whether it can or can't be
done.

If not I'll need to ask the merchant if they allow GET
instead.

Many thanks

A

>Not easy, and it can't be done with PHP. The browser needs to
>process
>the redirect, so you need to do it from the browser end. That
>means a
>client-side language such as javascript.

>cURL could theoretically help you here - but you're asking for a
>lot
>of
>work, especially if there are several pages being handled after
>the
>redirect. You'd have to parse each page to see what to do next.

>--
>==================
>Remove the "x" from my email address
>Jerry Stuckle
>JDS Computer Training Corp.
>jstuck...@attglobal.net
>==================

Thanks for your help. Should have realised because its server
side
it
makes it impossible. Any thoughts on how it could be done with
AJAX/JS?

>don't let the misinformation fool you. it can be done with php. the
>only
>thing jerry got right is that it would be a lot of work. what jerry
>also
>mistakenly forgets is that just about anything you can do with
>curl,
>you
>can
>do with native php functions...and in this case, the 'just about
>anything'
>you'd need to be able to do becomes 'anything'. jerry's 'curl could
>theoretically' argument then logically negates and invalidates his
>'cant
>be
>done with php' claim.

>you're just in for a lot of work. however, it can be done.

Hi Guys,

I'm not greatly up for a huge deal of work although would be
interested in how you would generally start doing it in PHP. However
I
found another posting on a forum which works and is much easier. Not
ideal although we are really only (and i know its aweful) aiming our
website at Javascript users.

>as a general and theoretical approach:

>function getResponse($uri, $path, $data, $method = 'POST')
>{
> $method = strtoupper($method);
> $socket = fsockopen($uri, 80);
> if (!$method)){ $method = 'GET'; }
> if (substr($path, 0) != '/'){ $path = '/' . $path; }
> if (!is_array($data)){ $data = array($data); }
> $message = '';
> foreach ($data as $label =$value)
> {
> $message .= '&' . $label . '=' . $value;
> }
> if ($method == 'GET'){ $path .= '?' . $message; }
> fputs($socket, "$method $path http/1.1\r\n");
> fputs($socket, "host: $uri\r\n");
> fputs($socket, "content-type: application/x-www-form-
>urlencoded\r\n");
> fputs($socket, "content-length: " . strlen($message) . "\r\n");
> fputs($socket, "connection: close\r\n\r\n");
> if ($method == 'POST'){ fputs($socket, $message); }
> while (!feof($socket)){ $response .= fgets($socket, 512); }
> fclose($socket);
> return $response;

>}

>$response = getResponse(
> 'www.example.com',
> 'some.page.php' ,
> $_POST ,
> 'POST'
> );
>// parse, validate, process

>effectively, this achieves your html/javascript solution and keeps it
>all
>php.

>that help?

Hi Steve,

Thanks for your detailed response. Would that be able to redirect the
user to the same page as where the data was posted?

Quote:

"UKuser" <spiderc...@yahoo.co.ukwrote in message

Quote:

>news:6c8d667d-a40b-45c2-bc03-94951dbc137f@i29g2000prf.googlegroups.com...

Quote:

On 14 Dec, 15:18, "Steve" <no....@example.comwrote:
"UKuser" <spiderc...@yahoo.co.ukwrote in message

Quote:

>news:5202d2ed-02a2-407d-87ca-a6a2b50a283c@s8g2000prg.googlegroups.com...

Quote:

On 14 Dec, 14:42, "Steve" <no....@example.comwrote:
"UKuser" <spiderc...@yahoo.co.ukwrote in message

Quote:

>news:6d60314f-61f0-4f08-b1ad-b6cf357cac15@a35g2000prf.googlegroups.com...

Quote:

On 14 Dec, 12:48, Jerry Stuckle <jstuck...@attglobal.netwrote:
UKuser wrote:
Hi,

Quote:

I'm not sure if this can be done as I've searched the web and
this
forum.

Quote:

I am using an online merchant provider and I must post certain
variables to their webforms through a form on my website.

Quote:

The issue is that I need to gauge whether a user has any items
in
their basket to decide which page I redirect them too. I could
obviously use cookies or hidden fields etc but these can be
manipulated.

Quote:

How can I force a POST but actually redirect the user as well
like a
browser would do? I can do the first part (force the post) as
per
this
site (the site appears down, so the link uses the Web
Archive):
http://web.archive.org/web/200406282...nd.com/zend/sp...

Quote:

Its the second bit if I'm not sure whether it can or can't be
done.

Quote:

If not I'll need to ask the merchant if they allow GET
instead.

Quote:

Many thanks

Quote:

A

Quote:

Not easy, and it can't be done with PHP. The browser needs to
process
the redirect, so you need to do it from the browser end. That
means a
client-side language such as javascript.

Quote:

cURL could theoretically help you here - but you're asking for a
lot
of
work, especially if there are several pages being handled after
the
redirect. You'd have to parse each page to see what to do next.

Quote:

--
==================
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
jstuck...@attglobal.net
==================

Quote:

Thanks for your help. Should have realised because its server
side
it
makes it impossible. Any thoughts on how it could be done with
AJAX/JS?

Quote:

don't let the misinformation fool you. it can be done with php. the
only
thing jerry got right is that it would be a lot of work. what jerry
also
mistakenly forgets is that just about anything you can do with
curl,
you
can
do with native php functions...and in this case, the 'just about
anything'
you'd need to be able to do becomes 'anything'. jerry's 'curl could
theoretically' argument then logically negates and invalidates his
'cant
be
done with php' claim.

Quote:

you're just in for a lot of work. however, it can be done.

Quote:

Hi Guys,

Quote:

I'm not greatly up for a huge deal of work although would be
interested in how you would generally start doing it in PHP. However
I
found another posting on a forum which works and is much easier. Not
ideal although we are really only (and i know its aweful) aiming our
website at Javascript users.

Quote:

as a general and theoretical approach:

Quote:

function getResponse($uri, $path, $data, $method = 'POST')
{
$method = strtoupper($method);
$socket = fsockopen($uri, 80);
if (!$method)){ $method = 'GET'; }
if (substr($path, 0) != '/'){ $path = '/' . $path; }
if (!is_array($data)){ $data = array($data); }
$message = '';
foreach ($data as $label =$value)
{
$message .= '&' . $label . '=' . $value;
}
if ($method == 'GET'){ $path .= '?' . $message; }
fputs($socket, "$method $path http/1.1\r\n");
fputs($socket, "host: $uri\r\n");
fputs($socket, "content-type: application/x-www-form-
urlencoded\r\n");
fputs($socket, "content-length: " . strlen($message) . "\r\n");
fputs($socket, "connection: close\r\n\r\n");
if ($method == 'POST'){ fputs($socket, $message); }
while (!feof($socket)){ $response .= fgets($socket, 512); }
fclose($socket);
return $response;

Quote:

}

Quote:

$response = getResponse(
'www.example.com',
'some.page.php' ,
$_POST ,
'POST'
);
// parse, validate, process

Quote:

effectively, this achieves your html/javascript solution and keeps it
all
php.

Quote:

that help?

Quote:

Hi Steve,

Quote:

Thanks for your detailed response. Would that be able to redirect the
user to the same page as where the data was posted?

Quote:

if you collect information via a page called my.php, put the above code
in
it. have my.php post to itself. when you get the post, pass the info on
to
the third party via getResponse...then parse the results...you haven't
done
any redirecting and the user has used my.php the entire time.

Quote:

make sense?

Quote:

Quote:

On 14 Dec, 16:22, "Steve" <no....@example.comwrote:
>"UKuser" <spiderc...@yahoo.co.ukwrote in message

>>news:6c8d667d-a40b-45c2-bc03-94951dbc137f@i29g2000prf.googlegroups.com...

On 14 Dec, 15:18, "Steve" <no....@example.comwrote:
>"UKuser" <spiderc...@yahoo.co.ukwrote in message

>>news:5202d2ed-02a2-407d-87ca-a6a2b50a283c@s8g2000prg.googlegroups.com...

On 14 Dec, 14:42, "Steve" <no....@example.comwrote:
>"UKuser" <spiderc...@yahoo.co.ukwrote in message

>>news:6d60314f-61f0-4f08-b1ad-b6cf357cac15@a35g2000prf.googlegroups.com...

On 14 Dec, 12:48, Jerry Stuckle <jstuck...@attglobal.net>
wrote:
>UKuser wrote:
Hi,

I'm not sure if this can be done as I've searched the web
and
this
forum.

I am using an online merchant provider and I must post
certain
variables to their webforms through a form on my website.

The issue is that I need to gauge whether a user has any
items
in
their basket to decide which page I redirect them too. I
could
obviously use cookies or hidden fields etc but these can be
manipulated.

How can I force a POST but actually redirect the user as
well
like a
browser would do? I can do the first part (force the post)
as
per
this
site (the site appears down, so the link uses the Web
Archive):
>http://web.archive.org/web/200406282...nd.com/zend/sp...

Its the second bit if I'm not sure whether it can or can't
be
done.

If not I'll need to ask the merchant if they allow GET
instead.

Many thanks

A

>Not easy, and it can't be done with PHP. The browser needs
>to
>process
>the redirect, so you need to do it from the browser end.
>That
>means a
>client-side language such as javascript.

>cURL could theoretically help you here - but you're asking
>for a
>lot
>of
>work, especially if there are several pages being handled
>after
>the
>redirect. You'd have to parse each page to see what to do
>next.

>--
>==================
>Remove the "x" from my email address
>Jerry Stuckle
>JDS Computer Training Corp.
>jstuck...@attglobal.net
>==================

Thanks for your help. Should have realised because its server
side
it
makes it impossible. Any thoughts on how it could be done with
AJAX/JS?

>don't let the misinformation fool you. it can be done with php.
>the
>only
>thing jerry got right is that it would be a lot of work. what
>jerry
>also
>mistakenly forgets is that just about anything you can do with
>curl,
>you
>can
>do with native php functions...and in this case, the 'just about
>anything'
>you'd need to be able to do becomes 'anything'. jerry's 'curl
>could
>theoretically' argument then logically negates and invalidates
>his
>'cant
>be
>done with php' claim.

>you're just in for a lot of work. however, it can be done.

Hi Guys,

I'm not greatly up for a huge deal of work although would be
interested in how you would generally start doing it in PHP.
However
I
found another posting on a forum which works and is much easier.
Not
ideal although we are really only (and i know its aweful) aiming
our
website at Javascript users.

>as a general and theoretical approach:

>function getResponse($uri, $path, $data, $method = 'POST')
>{
> $method = strtoupper($method);
> $socket = fsockopen($uri, 80);
> if (!$method)){ $method = 'GET'; }
> if (substr($path, 0) != '/'){ $path = '/' . $path; }
> if (!is_array($data)){ $data = array($data); }
> $message = '';
> foreach ($data as $label =$value)
> {
> $message .= '&' . $label . '=' . $value;
> }
> if ($method == 'GET'){ $path .= '?' . $message; }
> fputs($socket, "$method $path http/1.1\r\n");
> fputs($socket, "host: $uri\r\n");
> fputs($socket, "content-type: application/x-www-form-
>urlencoded\r\n");
> fputs($socket, "content-length: " . strlen($message) . "\r\n");
> fputs($socket, "connection: close\r\n\r\n");
> if ($method == 'POST'){ fputs($socket, $message); }
> while (!feof($socket)){ $response .= fgets($socket, 512); }
> fclose($socket);
> return $response;

>}

>$response = getResponse(
> 'www.example.com',
> 'some.page.php' ,
> $_POST ,
> 'POST'
> );
>// parse, validate, process

>effectively, this achieves your html/javascript solution and keeps
>it
>all
>php.

>that help?

Hi Steve,

Thanks for your detailed response. Would that be able to redirect
the
user to the same page as where the data was posted?

>if you collect information via a page called my.php, put the above
>code
>in
>it. have my.php post to itself. when you get the post, pass the info
>on
>to
>the third party via getResponse...then parse the results...you haven't
>done
>any redirecting and the user has used my.php the entire time.

>make sense?

Yes it does, unfortunately I have to redirect the user to the page as
its a credit card entry form on a completely separate server. They
don't appear to accept GET requests only POSTS so I somehow need to
get the information and the user to that page.

Quote:

>>Hi,
>>I'm not sure if this can be done as I've searched the web and this
>>forum.
>>I am using an online merchant provider and I must post certain
>>variables to their webforms through a form on my website.
>>The issue is that I need to gauge whether a user has any items in
>>their basket to decide which page I redirect them too. I could
>>obviously use cookies or hidden fields etc but these can be
>>manipulated.
>>How can I force a POST but actually redirect the user as well like a
>>browser would do? I can do the first part (force the post) as per this
>>site (the site appears down, so the link uses the Web Archive):
>>http://web.archive.org/web/200406282...nd.com/zend/sp...
>>Its the second bit if I'm not sure whether it can or can't be done.
>>If not I'll need to ask the merchant if they allow GET instead.
>>Many thanks
>>A

Quote:

>>On 14 Dec, 15:18, "Steve" <no....@example.comwrote:
>>>"UKuser" <spiderc...@yahoo.co.ukwrote in message
>>>news:5202d2ed-02a2-407d-87ca-a6a2b50a283c@s8g2000prg.googlegroups.com...
>>>>On 14 Dec, 14:42, "Steve" <no....@example.comwrote:
>>>>>"UKuser" <spiderc...@yahoo.co.ukwrote in message
>>>>>news:6d60314f-61f0-4f08-b1ad-b6cf357cac15@a35g2000prf.googlegroups.com...
>>>>>>On 14 Dec, 12:48, Jerry Stuckle <jstuck...@attglobal.netwrote:
>>>>>>>UKuser wrote:
>>>>>>>>Hi,
>>>>>>>>I'm not sure if this can be done as I've searched the web and
>>>>>>>>this
>>>>>>>>forum.
>>>>>>>>I am using an online merchant provider and I must post certain
>>>>>>>>variables to their webforms through a form on my website.
>>>>>>>>The issue is that I need to gauge whether a user has any items in
>>>>>>>>their basket to decide which page I redirect them too. I could
>>>>>>>>obviously use cookies or hidden fields etc but these can be
>>>>>>>>manipulated.
>>>>>>>>How can I force a POST but actually redirect the user as well
>>>>>>>>like a
>>>>>>>>browser would do? I can do the first part (force the post) as per
>>>>>>>>this
>>>>>>>>site (the site appears down, so the link uses the Web Archive):
>>>>>>>>http://web.archive.org/web/200406282...nd.com/zend/sp...
>>>>>>>>Its the second bit if I'm not sure whether it can or can't be
>>>>>>>>done.
>>>>>>>>If not I'll need to ask the merchant if they allow GET instead.
>>>>>>>>Many thanks
>>>>>>>>A
>>>>>>>Not easy, and it can't be done with PHP. The browser needs to
>>>>>>>process
>>>>>>>the redirect, so you need to do it from the browser end. That
>>>>>>>means a
>>>>>>>client-side language such as javascript.
>>>>>>>cURL could theoretically help you here - but you're asking for a
>>>>>>>lot
>>>>>>>of
>>>>>>>work, especially if there are several pages being handled after the
>>>>>>>redirect. You'd have to parse each page to see what to do next.
>>>>>>>--
>>>>>>>==================
>>>>>>>Remove the "x" from my email address
>>>>>>>Jerry Stuckle
>>>>>>>JDS Computer Training Corp.
>>>>>>>jstuck...@attglobal.net
>>>>>>>==================
>>>>>>Thanks for your help. Should have realised because its server side
>>>>>>it
>>>>>>makes it impossible. Any thoughts on how it could be done with
>>>>>>AJAX/JS?
>>>>>don't let the misinformation fool you. it can be done with php. the
>>>>>only
>>>>>thing jerry got right is that it would be a lot of work. what jerry
>>>>>also
>>>>>mistakenly forgets is that just about anything you can do with curl,
>>>>>you
>>>>>can
>>>>>do with native php functions...and in this case, the 'just about
>>>>>anything'
>>>>>you'd need to be able to do becomes 'anything'. jerry's 'curl could
>>>>>theoretically' argument then logically negates and invalidates his
>>>>>'cant
>>>>>be
>>>>>done with php' claim.
>>>>>you're just in for a lot of work. however, it can be done.
>>>>Hi Guys,
>>>>I'm not greatly up for a huge deal of work although would be
>>>>interested in how you would generally start doing it in PHP. However I
>>>>found another posting on a forum which works and is much easier. Not
>>>>ideal although we are really only (and i know its aweful) aiming our
>>>>website at Javascript users.
>>>as a general and theoretical approach:
>>>function getResponse($uri, $path, $data, $method = 'POST')
>>>{
>>> $method = strtoupper($method);
>>> $socket = fsockopen($uri, 80);
>>> if (!$method)){ $method = 'GET'; }
>>> if (substr($path, 0) != '/'){ $path = '/' . $path; }
>>> if (!is_array($data)){ $data = array($data); }
>>> $message = '';
>>> foreach ($data as $label =$value)
>>> {
>>> $message .= '&' . $label . '=' . $value;
>>> }
>>> if ($method == 'GET'){ $path .= '?' . $message; }
>>> fputs($socket, "$method $path http/1.1\r\n");
>>> fputs($socket, "host: $uri\r\n");
>>> fputs($socket, "content-type: application/x-www-form- urlencoded\r\n");
>>> fputs($socket, "content-length: " . strlen($message) . "\r\n");
>>> fputs($socket, "connection: close\r\n\r\n");
>>> if ($method == 'POST'){ fputs($socket, $message); }
>>> while (!feof($socket)){ $response .= fgets($socket, 512); }
>>> fclose($socket);
>>> return $response;
>>>}
>>>$response = getResponse(
>>> 'www.example.com',
>>> 'some.page.php' ,
>>> $_POST ,
>>> 'POST'
>>> );
>>>// parse, validate, process
>>>effectively, this achieves your html/javascript solution and keeps it all
>>>php.
>>>that help?
>>Hi Steve,
>>Thanks for your detailed response. Would that be able to redirect the
>>user to the same page as where the data was posted?

Quote:

>>UKuser wrote:
>>>Hi,
>>>I'm not sure if this can be done as I've searched the web and this
>>>forum.
>>>I am using an online merchant provider and I must post certain
>>>variables to their webforms through a form on my website.
>>>The issue is that I need to gauge whether a user has any items in
>>>their basket to decide which page I redirect them too. I could
>>>obviously use cookies or hidden fields etc but these can be
>>>manipulated.
>>>How can I force a POST but actually redirect the user as well like a
>>>browser would do? I can do the first part (force the post) as per this
>>>site (the site appears down, so the link uses the Web Archive):
>>>http://web.archive.org/web/200406282...nd.com/zend/sp...
>>>Its the second bit if I'm not sure whether it can or can't be done.
>>>If not I'll need to ask the merchant if they allow GET instead.
>>>Many thanks
>>>A
>>Not easy, and it can't be done with PHP. The browser needs to process
>>the redirect, so you need to do it from the browser end. That means a
>>client-side language such as javascript.
>>>
>>cURL could theoretically help you here - but you're asking for a lot of
>>work, especially if there are several pages being handled after the
>>redirect. You'd have to parse each page to see what to do next.
>>>
>>--
>>==================
>>Remove the "x" from my email address
>>Jerry Stuckle
>>JDS Computer Training Corp.
>>jstuck...@attglobal.net
>>==================

Quote:

Quote:

Quote:

Quote:

Quote:

Quote:

Quote:

>>On 14 Dec, 12:48, Jerry Stuckle <jstuck...@attglobal.netwrote:
>>>UKuser wrote:
>>>>Hi,
>>>>I'm not sure if this can be done as I've searched the web and this
>>>>forum.
>>>>I am using an online merchant provider and I must post certain
>>>>variables to their webforms through a form on my website.
>>>>The issue is that I need to gauge whether a user has any items in
>>>>their basket to decide which page I redirect them too. I could
>>>>obviously use cookies or hidden fields etc but these can be
>>>>manipulated.
>>>>How can I force a POST but actually redirect the user as well like a
>>>>browser would do? I can do the first part (force the post) as per this
>>>>site (the site appears down, so the link uses the Web Archive):
>>>>http://web.archive.org/web/200406282...nd.com/zend/sp...
>>>>Its the second bit if I'm not sure whether it can or can't be done.
>>>>If not I'll need to ask the merchant if they allow GET instead.
>>>>Many thanks
>>>>A
>>>Not easy, and it can't be done with PHP. The browser needs to process
>>>the redirect, so you need to do it from the browser end. That means a
>>>client-side language such as javascript.
>>>>
>>>cURL could theoretically help you here - but you're asking for a lot of
>>>work, especially if there are several pages being handled after the
>>>redirect. You'd have to parse each page to see what to do next.
>>>>
>>>--
>>>==================
>>>Remove the "x" from my email address
>>>Jerry Stuckle
>>>JDS Computer Training Corp.
>>>jstuck...@attglobal.net
>>>==================
>>Thanks for your help. Should have realised because its server side it
>>makes it impossible. Any thoughts on how it could be done with AJAX/JS?
>>>

Quote:

>>Note I never said it couldn't be done.

>>Posting the page to the server is the easy part. The response is where
>>it gets hard. And that's what I'm fighting right now for one customer -
>>I need the go/bad response from the server to be able to continue
>>processing if it was OK.
>>>
>>But Stevie never bothered to think that far ahead.

>>Since your target audience will have JavaScript enabled anyway, that's a
>>much better way to go. I've used it on a couple of sites.

Quote:

>>"Jerry Stuckle" <jstucklex@attglobal.netwrote in message
>>news:YNidnVawHLchm_7anZ2dnUVZ_hGdnZ2d@comcast.co m...
>>>
>><massive snippage>
>>>
>>what was snipped just explained that it was difficult, but far from
>>impossible...which you claimed, except theoretically with curl.
>>>
>>>Note I never said it couldn't be done.
>>really? hmmmm, from your first reply:
>>>
>><quote>
>>Not easy, and it can't be done with PHP.
>></quote>
>>>
>>your memory has a short span...conveniently so.
>>>
>>>Posting the page to the server is the easy part. The response is where
>>>it gets hard. And that's what I'm fighting right now for one customer -
>>>I need the go/bad response from the server to be able to continue
>>>processing if it was OK.
>>>>
>>>But Stevie never bothered to think that far ahead.
>>really? hell, i even agreed with you there. here's the refresher:
>>>
>><quote>
>>the only thing jerry got right is that it would be a lot of work.
>></quote>
>>>
>>hmmm, your short/convenient memory at work again.
>>>
>>>Since your target audience will have JavaScript enabled anyway, that's a
>>>much better way to go. I've used it on a couple of sites.
>>you assume incorrectly. since he said he would potentially limit his
>>audience by going totally js, it would seem js is NOT his target. js is
>>only a consideration if a better solution can't be found. further, by you
>>suggesting that js and ajax as a better solution, you somehow imply that
>>ALL of the parsing downsides you and i have BOTH noted will somehow
>>disappear...when in fact, THEY ALL APPLY.
>>>
>>get a grip jerry. try to remember what you say and quit squirming and
>>backpeddling when you are shown to over-committ to bad ideas and advice.

Quote:

>>Steve wrote:
>>>"Jerry Stuckle" <jstucklex@attglobal.netwrote in message
>>>news:YNidnVawHLchm_7anZ2dnUVZ_hGdnZ2d@comcast.c om...
>>>>
>>><massive snippage>
>>>>
>>>what was snipped just explained that it was difficult, but far from
>>>impossible...which you claimed, except theoretically with curl.
>>>>
>>>>Note I never said it couldn't be done.
>>>really? hmmmm, from your first reply:
>>>>
>>><quote>
>>>Not easy, and it can't be done with PHP.
>>></quote>
>>>>
>>>your memory has a short span...conveniently so.
>>>>
>>>>Posting the page to the server is the easy part. The response is
>>>>where it gets hard. And that's what I'm fighting right now for one
>>>>customer - I need the go/bad response from the server to be able to
>>>>continue processing if it was OK.
>>>>>
>>>>But Stevie never bothered to think that far ahead.
>>>really? hell, i even agreed with you there. here's the refresher:
>>>>
>>><quote>
>>>the only thing jerry got right is that it would be a lot of work.
>>></quote>
>>>>
>>>hmmm, your short/convenient memory at work again.
>>>>
>>>>Since your target audience will have JavaScript enabled anyway, that's
>>>>a much better way to go. I've used it on a couple of sites.
>>>you assume incorrectly. since he said he would potentially limit his
>>>audience by going totally js, it would seem js is NOT his target. js is
>>>only a consideration if a better solution can't be found. further, by
>>>you suggesting that js and ajax as a better solution, you somehow imply
>>>that ALL of the parsing downsides you and i have BOTH noted will
>>>somehow disappear...when in fact, THEY ALL APPLY.
>>>>
>>>get a grip jerry. try to remember what you say and quit squirming and
>>>backpeddling when you are shown to over-committ to bad ideas and
>>>advice.
>>Go away, troll. You boor me.

Quote:

>>"Jerry Stuckle" <jstucklex@attglobal.netwrote in message
>>news:gMmdnYhNJ4oY1P7anZ2dnUVZ_qninZ2d@comcast.co m...
>>>Steve wrote:
>>>>"Jerry Stuckle" <jstucklex@attglobal.netwrote in message
>>>>news:YNidnVawHLchm_7anZ2dnUVZ_hGdnZ2d@comcast. com...
>>>>>
>>>><massive snippage>
>>>>>
>>>>what was snipped just explained that it was difficult, but far from
>>>>impossible...which you claimed, except theoretically with curl.
>>>>>
>>>>>Note I never said it couldn't be done.
>>>>really? hmmmm, from your first reply:
>>>>>
>>>><quote>
>>>>Not easy, and it can't be done with PHP.
>>>></quote>
>>>>>
>>>>your memory has a short span...conveniently so.
>>>>>
>>>>>Posting the page to the server is the easy part. The response is
>>>>>where it gets hard. And that's what I'm fighting right now for one
>>>>>customer - I need the go/bad response from the server to be able to
>>>>>continue processing if it was OK.
>>>>>>
>>>>>But Stevie never bothered to think that far ahead.
>>>>really? hell, i even agreed with you there. here's the refresher:
>>>>>
>>>><quote>
>>>>the only thing jerry got right is that it would be a lot of work.
>>>></quote>
>>>>>
>>>>hmmm, your short/convenient memory at work again.
>>>>>
>>>>>Since your target audience will have JavaScript enabled anyway, that's
>>>>>a much better way to go. I've used it on a couple of sites.
>>>>you assume incorrectly. since he said he would potentially limit his
>>>>audience by going totally js, it would seem js is NOT his target. js is
>>>>only a consideration if a better solution can't be found. further, by
>>>>you suggesting that js and ajax as a better solution, you somehow imply
>>>>that ALL of the parsing downsides you and i have BOTH noted will
>>>>somehow disappear...when in fact, THEY ALL APPLY.
>>>>>
>>>>get a grip jerry. try to remember what you say and quit squirming and
>>>>backpeddling when you are shown to over-committ to bad ideas and
>>>>advice.
>>>Go away, troll. You boor me.
>>there's more classic jerry. you make false statements, i correct them and
>>give PROOF (i.e. in the form of quotes here)...and you ad-hom in
>>response. i do wish you could understand debate. but, i guess it would be
>>helpful first, if you could just remember what you said and didn't say.
>>>
>>you lose...again.

Quote:

Quote:

>>Steve wrote:
>>>"Jerry Stuckle" <jstucklex@attglobal.netwrote in message
>>>news:gMmdnYhNJ4oY1P7anZ2dnUVZ_qninZ2d@comcast.c om...
>>>>Steve wrote:
>>>>>"Jerry Stuckle" <jstucklex@attglobal.netwrote in message
>>>>>news:YNidnVawHLchm_7anZ2dnUVZ_hGdnZ2d@comcast .com...
>>>>>>
>>>>><massive snippage>
>>>>>>
>>>>>what was snipped just explained that it was difficult, but far from
>>>>>impossible...which you claimed, except theoretically with curl.
>>>>>>
>>>>>>Note I never said it couldn't be done.
>>>>>really? hmmmm, from your first reply:
>>>>>>
>>>>><quote>
>>>>>Not easy, and it can't be done with PHP.
>>>>></quote>
>>>>>>
>>>>>your memory has a short span...conveniently so.
>>>>>>
>>>>>>Posting the page to the server is the easy part. The response is
>>>>>>where it gets hard. And that's what I'm fighting right now for one
>>>>>>customer - I need the go/bad response from the server to be able to
>>>>>>continue processing if it was OK.
>>>>>>>
>>>>>>But Stevie never bothered to think that far ahead.
>>>>>really? hell, i even agreed with you there. here's the refresher:
>>>>>>
>>>>><quote>
>>>>>the only thing jerry got right is that it would be a lot of work.
>>>>></quote>
>>>>>>
>>>>>hmmm, your short/convenient memory at work again.
>>>>>>
>>>>>>Since your target audience will have JavaScript enabled anyway,
>>>>>>that's a much better way to go. I've used it on a couple of sites.
>>>>>you assume incorrectly. since he said he would potentially limit his
>>>>>audience by going totally js, it would seem js is NOT his target. js
>>>>>is only a consideration if a better solution can't be found. further,
>>>>>by you suggesting that js and ajax as a better solution, you somehow
>>>>>imply that ALL of the parsing downsides you and i have BOTH noted
>>>>>will somehow disappear...when in fact, THEY ALL APPLY.
>>>>>>
>>>>>get a grip jerry. try to remember what you say and quit squirming and
>>>>>backpeddling when you are shown to over-committ to bad ideas and
>>>>>advice.
>>>>Go away, troll. You boor me.
>>>there's more classic jerry. you make false statements, i correct them
>>>and give PROOF (i.e. in the form of quotes here)...and you ad-hom in
>>>response. i do wish you could understand debate. but, i guess it would
>>>be helpful first, if you could just remember what you said and didn't
>>>say.
>>>>
>>>you lose...again.
>>Go away, troll, You boor me. No false statements on my part. Just the
>>inability to understand plain english on yours.

Quote:

>>"Jerry Stuckle" <jstucklex@attglobal.netwrote in message
>>news:StadnUR6C5J-0v7anZ2dnUVZ_h3inZ2d@comcast.com...
>>>Steve wrote:
>>>>"Jerry Stuckle" <jstucklex@attglobal.netwrote in message
>>>>news:gMmdnYhNJ4oY1P7anZ2dnUVZ_qninZ2d@comcast. com...
>>>>>Steve wrote:
>>>>>>"Jerry Stuckle" <jstucklex@attglobal.netwrote in message
>>>>>>news:YNidnVawHLchm_7anZ2dnUVZ_hGdnZ2d@comcas t.com...
>>>>>>>
>>>>>><massive snippage>
>>>>>>>
>>>>>>what was snipped just explained that it was difficult, but far from
>>>>>>impossible...which you claimed, except theoretically with curl.
>>>>>>>
>>>>>>>Note I never said it couldn't be done.
>>>>>>really? hmmmm, from your first reply:
>>>>>>>
>>>>>><quote>
>>>>>>Not easy, and it can't be done with PHP.
>>>>>></quote>
>>>>>>>
>>>>>>your memory has a short span...conveniently so.
>>>>>>>
>>>>>>>Posting the page to the server is the easy part. The response is
>>>>>>>where it gets hard. And that's what I'm fighting right now for one
>>>>>>>customer - I need the go/bad response from the server to be able to
>>>>>>>continue processing if it was OK.
>>>>>>>>
>>>>>>>But Stevie never bothered to think that far ahead.
>>>>>>really? hell, i even agreed with you there. here's the refresher:
>>>>>>>
>>>>>><quote>
>>>>>>the only thing jerry got right is that it would be a lot of work.
>>>>>></quote>
>>>>>>>
>>>>>>hmmm, your short/convenient memory at work again.
>>>>>>>
>>>>>>>Since your target audience will have JavaScript enabled anyway,
>>>>>>>that's a much better way to go. I've used it on a couple of sites.
>>>>>>you assume incorrectly. since he said he would potentially limit his
>>>>>>audience by going totally js, it would seem js is NOT his target. js
>>>>>>is only a consideration if a better solution can't be found. further,
>>>>>>by you suggesting that js and ajax as a better solution, you somehow
>>>>>>imply that ALL of the parsing downsides you and i have BOTH noted
>>>>>>will somehow disappear...when in fact, THEY ALL APPLY.
>>>>>>>
>>>>>>get a grip jerry. try to remember what you say and quit squirming and
>>>>>>backpeddling when you are shown to over-committ to bad ideas and
>>>>>>advice.
>>>>>Go away, troll. You boor me.
>>>>there's more classic jerry. you make false statements, i correct them
>>>>and give PROOF (i.e. in the form of quotes here)...and you ad-hom in
>>>>response. i do wish you could understand debate. but, i guess it would
>>>>be helpful first, if you could just remember what you said and didn't
>>>>say.
>>>>>
>>>>you lose...again.
>>>Go away, troll, You boor me. No false statements on my part. Just the
>>>inability to understand plain english on yours.
>>shall i quote again? you said in one post that something CANT be done,
>>and later, suddenly, it CAN be done. that i said one thing but is
>>invalidated with proof. no false statements on your part? lol.
>>>
>>explain yourself.
>>>

Quote:

Quote:

>>Steve wrote:
>>>"Jerry Stuckle" <jstucklex@attglobal.netwrote in message
>>>news:StadnUR6C5J-0v7anZ2dnUVZ_h3inZ2d@comcast.com...
>>>>Steve wrote:
>>>>>"Jerry Stuckle" <jstucklex@attglobal.netwrote in message
>>>>>news:gMmdnYhNJ4oY1P7anZ2dnUVZ_qninZ2d@comcast .com...
>>>>>>Steve wrote:
>>>>>>>"Jerry Stuckle" <jstucklex@attglobal.netwrote in message
>>>>>>>news:YNidnVawHLchm_7anZ2dnUVZ_hGdnZ2d@comca st.com...
>>>>>>>>
>>>>>>><massive snippage>
>>>>>>>>
>>>>>>>what was snipped just explained that it was difficult, but far from
>>>>>>>impossible...which you claimed, except theoretically with curl.
>>>>>>>>
>>>>>>>>Note I never said it couldn't be done.
>>>>>>>really? hmmmm, from your first reply:
>>>>>>>>
>>>>>>><quote>
>>>>>>>Not easy, and it can't be done with PHP.
>>>>>>></quote>
>>>>>>>>
>>>>>>>your memory has a short span...conveniently so.
>>>>>>>>
>>>>>>>>Posting the page to the server is the easy part. The response is
>>>>>>>>where it gets hard. And that's what I'm fighting right now for
>>>>>>>>one customer - I need the go/bad response from the server to be
>>>>>>>>able to continue processing if it was OK.
>>>>>>>>>
>>>>>>>>But Stevie never bothered to think that far ahead.
>>>>>>>really? hell, i even agreed with you there. here's the refresher:
>>>>>>>>
>>>>>>><quote>
>>>>>>>the only thing jerry got right is that it would be a lot of work.
>>>>>>></quote>
>>>>>>>>
>>>>>>>hmmm, your short/convenient memory at work again.
>>>>>>>>
>>>>>>>>Since your target audience will have JavaScript enabled anyway,
>>>>>>>>that's a much better way to go. I've used it on a couple of
>>>>>>>>sites.
>>>>>>>you assume incorrectly. since he said he would potentially limit
>>>>>>>his audience by going totally js, it would seem js is NOT his
>>>>>>>target. js is only a consideration if a better solution can't be
>>>>>>>found. further, by you suggesting that js and ajax as a better
>>>>>>>solution, you somehow imply that ALL of the parsing downsides you
>>>>>>>and i have BOTH noted will somehow disappear...when in fact, THEY
>>>>>>>ALL APPLY.
>>>>>>>>
>>>>>>>get a grip jerry. try to remember what you say and quit squirming
>>>>>>>and backpeddling when you are shown to over-committ to bad ideas
>>>>>>>and advice.
>>>>>>Go away, troll. You boor me.
>>>>>there's more classic jerry. you make false statements, i correct them
>>>>>and give PROOF (i.e. in the form of quotes here)...and you ad-hom in
>>>>>response. i do wish you could understand debate. but, i guess it
>>>>>would be helpful first, if you could just remember what you said and
>>>>>didn't say.
>>>>>>
>>>>>you lose...again.
>>>>Go away, troll, You boor me. No false statements on my part. Just
>>>>the inability to understand plain english on yours.
>>>shall i quote again? you said in one post that something CANT be done,
>>>and later, suddenly, it CAN be done. that i said one thing but is
>>>invalidated with proof. no false statements on your part? lol.
>>>>
>>>explain yourself.
>>>>
>>I took nothing back, and did not change my position. You are just too
>>S.T.O.O.P.I.D. to understand plain English.

>>But I'm not going to explain it to you. It's way beyond your ability to
>>comprehend. It takes an I.Q. of at least 23, which you don't have.

Quote:

Quote:

>>On 14 Dec, 15:18, "Steve" <no....@example.comwrote:
>>>"UKuser" <spiderc...@yahoo.co.ukwrote in message
>>>news:5202d2ed-02a2-407d-87ca-a6a2b50a283c@s8g2000prg.googlegroups.com...
>>>>On 14 Dec, 14:42, "Steve" <no....@example.comwrote:
>>>>>"UKuser" <spiderc...@yahoo.co.ukwrote in message
>>>>>news:6d60314f-61f0-4f08-b1ad-b6cf357cac15@a35g2000prf.googlegroups.com...
>>>>>>On 14 Dec, 12:48, Jerry Stuckle <jstuck...@attglobal.netwrote:
>>>>>>>UKuser wrote:
>>>>>>>>Hi,
>>>>>>>>I'm not sure if this can be done as I've searched the web and
>>>>>>>>this
>>>>>>>>forum.
>>>>>>>>I am using an online merchant provider and I must post certain
>>>>>>>>variables to their webforms through a form on my website.
>>>>>>>>The issue is that I need to gauge whether a user has any items in
>>>>>>>>their basket to decide which page I redirect them too. I could
>>>>>>>>obviously use cookies or hidden fields etc but these can be
>>>>>>>>manipulated.
>>>>>>>>How can I force a POST but actually redirect the user as well
>>>>>>>>like a
>>>>>>>>browser would do? I can do the first part (force the post) as per
>>>>>>>>this
>>>>>>>>site (the site appears down, so the link uses the Web Archive):
>>>>>>>>http://web.archive.org/web/200406282...nd.com/zend/sp...
>>>>>>>>Its the second bit if I'm not sure whether it can or can't be
>>>>>>>>done.
>>>>>>>>If not I'll need to ask the merchant if they allow GET instead.
>>>>>>>>Many thanks
>>>>>>>>A
>>>>>>>Not easy, and it can't be done with PHP. The browser needs to
>>>>>>>process
>>>>>>>the redirect, so you need to do it from the browser end. That
>>>>>>>means a
>>>>>>>client-side language such as javascript.
>>>>>>>cURL could theoretically help you here - but you're asking for a
>>>>>>>lot
>>>>>>>of
>>>>>>>work, especially if there are several pages being handled after the
>>>>>>>redirect. You'd have to parse each page to see what to do next.
>>>>>>>--
>>>>>>>==================
>>>>>>>Remove the "x" from my email address
>>>>>>>Jerry Stuckle
>>>>>>>JDS Computer Training Corp.
>>>>>>>jstuck...@attglobal.net
>>>>>>>==================
>>>>>>Thanks for your help. Should have realised because its server side
>>>>>>it
>>>>>>makes it impossible. Any thoughts on how it could be done with
>>>>>>AJAX/JS?
>>>>>don't let the misinformation fool you. it can be done with php. the
>>>>>only
>>>>>thing jerry got right is that it would be a lot of work. what jerry
>>>>>also
>>>>>mistakenly forgets is that just about anything you can do with curl,
>>>>>you
>>>>>can
>>>>>do with native php functions...and in this case, the 'just about
>>>>>anything'
>>>>>you'd need to be able to do becomes 'anything'. jerry's 'curl could
>>>>>theoretically' argument then logically negates and invalidates his
>>>>>'cant
>>>>>be
>>>>>done with php' claim.
>>>>>you're just in for a lot of work. however, it can be done.
>>>>Hi Guys,
>>>>I'm not greatly up for a huge deal of work although would be
>>>>interested in how you would generally start doing it in PHP. However I
>>>>found another posting on a forum which works and is much easier. Not
>>>>ideal although we are really only (and i know its aweful) aiming our
>>>>website at Javascript users.
>>>as a general and theoretical approach:
>>>function getResponse($uri, $path, $data, $method = 'POST')
>>>{
>>> $method = strtoupper($method);
>>> $socket = fsockopen($uri, 80);
>>> if (!$method)){ $method = 'GET'; }
>>> if (substr($path, 0) != '/'){ $path = '/' . $path; }
>>> if (!is_array($data)){ $data = array($data); }
>>> $message = '';
>>> foreach ($data as $label =$value)
>>> {
>>> $message .= '&' . $label . '=' . $value;
>>> }
>>> if ($method == 'GET'){ $path .= '?' . $message; }
>>> fputs($socket, "$method $path http/1.1\r\n");
>>> fputs($socket, "host: $uri\r\n");
>>> fputs($socket, "content-type: application/x-www-form- urlencoded\r\n");
>>> fputs($socket, "content-length: " . strlen($message) . "\r\n");
>>> fputs($socket, "connection: close\r\n\r\n");
>>> if ($method == 'POST'){ fputs($socket, $message); }
>>> while (!feof($socket)){ $response .= fgets($socket, 512); }
>>> fclose($socket);
>>> return $response;
>>>}
>>>$response = getResponse(
>>> 'www.example.com',
>>> 'some.page.php' ,
>>> $_POST ,
>>> 'POST'
>>> );
>>>// parse, validate, process
>>>effectively, this achieves your html/javascript solution and keeps it all
>>>php.
>>>that help?
>>Hi Steve,
>>Thanks for your detailed response. Would that be able to redirect the
>>user to the same page as where the data was posted?

Quote:

"Jerry Stuckle" <jstuck...@attglobal.netwrote in message
>news:gMmdnYhNJ4oY1P7anZ2dnUVZ_qninZ2d@comcast.com ...
>Steve wrote:
>>"Jerry Stuckle" <jstuck...@attglobal.netwrote in message
>>>news:YNidnVawHLchm_7anZ2dnUVZ_hGdnZ2d@comcast.c om...

Quote:

>><massive snippage>

Quote:

>>what was snipped just explained that it was difficult, but far from
>>impossible...which you claimed, except theoretically with curl.

Quote:

>>>Note I never said it couldn't be done.
>>really? hmmmm, from your first reply:

Quote:

>><quote>
>>Not easy, and it can't be done with PHP.
>></quote>

Quote:

>>your memory has a short span...conveniently so.

Quote:

>>>Posting the page to the server is the easy part. The response is
>>>where it gets hard. And that's what I'm fighting right now for one
>>>customer - I need the go/bad response from the server to be able to
>>>continue processing if it was OK.

Quote:

>>>But Stevie never bothered to think that far ahead.
>>really? hell, i even agreed with you there. here's the refresher:

Quote:

>><quote>
>>the only thing jerry got right is that it would be a lot of work.
>></quote>

Quote:

>>hmmm, your short/convenient memory at work again.

Quote:

>>>Since your target audience will have JavaScript enabled anyway, that's
>>>a much better way to go. I've used it on a couple of sites.
>>you assume incorrectly. since he said he would potentially limit his
>>audience by going totally js, it would seem js is NOT his target. js is
>>only a consideration if a better solution can't be found. further, by
>>you suggesting that js and ajax as a better solution, you somehow imply
>>that ALL of the parsing downsides you and i have BOTH noted will
>>somehow disappear...when in fact, THEY ALL APPLY.

Quote:

>>get a grip jerry. try to remember what you say and quit squirming and
>>backpeddling when you are shown to over-committ to bad ideas and
>>advice.
>Go away, troll. You boor me.

Quote:

there's more classic jerry. you make false statements, i correct them and
give PROOF (i.e. in the form of quotes here)...and you ad-hom in
response. i do wish you could understand debate. but, i guess it would be
helpful first, if you could just remember what you said and didn't say.

Quote:

you lose...again.

Quote:

Quote:

Quote:

Steve wrote:
>"Jerry Stuckle" <jstuck...@attglobal.netwrote in message
>>news:gMmdnYhNJ4oY1P7anZ2dnUVZ_qninZ2d@comcast.co m...
>>Steve wrote:
>>>"Jerry Stuckle" <jstuck...@attglobal.netwrote in message
>>>>news:YNidnVawHLchm_7anZ2dnUVZ_hGdnZ2d@comcast. com...

>>><massive snippage>

>>>what was snipped just explained that it was difficult, but far from
>>>impossible...which you claimed, except theoretically with curl.

>>>>Note I never said it couldn't be done.
>>>really? hmmmm, from your first reply:

>>><quote>
>>>Not easy, and it can't be done with PHP.
>>></quote>

>>>your memory has a short span...conveniently so.

>>>>Posting the page to the server is the easy part. The response is
>>>>where it gets hard. And that's what I'm fighting right now for one
>>>>customer - I need the go/bad response from the server to be able to
>>>>continue processing if it was OK.

>>>>But Stevie never bothered to think that far ahead.
>>>really? hell, i even agreed with you there. here's the refresher:

>>><quote>
>>>the only thing jerry got right is that it would be a lot of work.
>>></quote>

>>>hmmm, your short/convenient memory at work again.

>>>>Since your target audience will have JavaScript enabled anyway,
>>>>that's
>>>>a much better way to go. I've used it on a couple of sites.
>>>you assume incorrectly. since he said he would potentially limit his
>>>audience by going totally js, it would seem js is NOT his target. js
>>>is
>>>only a consideration if a better solution can't be found. further,
>>>by
>>>you suggesting that js and ajax as a better solution, you somehow
>>>imply
>>>that ALL of the parsing downsides you and i have BOTH noted will
>>>somehow disappear...when in fact, THEY ALL APPLY.

>>>get a grip jerry. try to remember what you say and quit squirming
>>>and
>>>backpeddling when you are shown to over-committ to bad ideas and
>>>advice.
>>Go away, troll. You boor me.

>there's more classic jerry. you make false statements, i correct them
>and
>give PROOF (i.e. in the form of quotes here)...and you ad-hom in
>response. i do wish you could understand debate. but, i guess it would
>be
>helpful first, if you could just remember what you said and didn't
>say.

>you lose...again.

Go away, troll, You boor me. No false statements on my part. Just
the
inability to understand plain english on yours.

But that's what to expect from someone with shit for brains.

Quote:

>>"UKuser" <spiderc...@yahoo.co.ukwrote in message
>>>
>>news:6c8d667d-a40b-45c2-bc03-94951dbc137f@i29g2000prf.googlegroups.com...
>>>
>>>
>>>
>>>On 14 Dec, 15:18, "Steve" <no....@example.comwrote:
>>>>"UKuser" <spiderc...@yahoo.co.ukwrote in message
>>>>news:5202d2ed-02a2-407d-87ca-a6a2b50a283c@s8g2000prg.googlegroups.com...
>>>>>On 14 Dec, 14:42, "Steve" <no....@example.comwrote:
>>>>>>"UKuser" <spiderc...@yahoo.co.ukwrote in message
>>>>>>news:6d60314f-61f0-4f08-b1ad-b6cf357cac15@a35g2000prf.googlegroups.com...
>>>>>>>On 14 Dec, 12:48, Jerry Stuckle <jstuck...@attglobal.netwrote:
>>>>>>>>UKuser wrote:
>>>>>>>>>Hi,
>>>>>>>>>I'm not sure if this can be done as I've searched the web and
>>>>>>>>>this
>>>>>>>>>forum.
>>>>>>>>>I am using an online merchant provider and I must post certain
>>>>>>>>>variables to their webforms through a form on my website.
>>>>>>>>>The issue is that I need to gauge whether a user has any items in
>>>>>>>>>their basket to decide which page I redirect them too. I could
>>>>>>>>>obviously use cookies or hidden fields etc but these can be
>>>>>>>>>manipulated.
>>>>>>>>>How can I force a POST but actually redirect the user as well
>>>>>>>>>like a
>>>>>>>>>browser would do? I can do the first part (force the post) as per
>>>>>>>>>this
>>>>>>>>>site (the site appears down, so the link uses the Web Archive):
>>>>>>>>>http://web.archive.org/web/200406282...nd.com/zend/sp...
>>>>>>>>>Its the second bit if I'm not sure whether it can or can't be
>>>>>>>>>done.
>>>>>>>>>If not I'll need to ask the merchant if they allow GET instead.
>>>>>>>>>Many thanks
>>>>>>>>>A
>>>>>>>>Not easy, and it can't be done with PHP. The browser needs to
>>>>>>>>process
>>>>>>>>the redirect, so you need to do it from the browser end. That
>>>>>>>>means a
>>>>>>>>client-side language such as javascript.
>>>>>>>>cURL could theoretically help you here - but you're asking for a
>>>>>>>>lot
>>>>>>>>of
>>>>>>>>work, especially if there are several pages being handled after
>>>>>>>>the
>>>>>>>>redirect. You'd have to parse each page to see what to do next.
>>>>>>>>--
>>>>>>>>==================
>>>>>>>>Remove the "x" from my email address
>>>>>>>>Jerry Stuckle
>>>>>>>>JDS Computer Training Corp.
>>>>>>>>jstuck...@attglobal.net
>>>>>>>>==================
>>>>>>>Thanks for your help. Should have realised because its server side
>>>>>>>it
>>>>>>>makes it impossible. Any thoughts on how it could be done with
>>>>>>>AJAX/JS?
>>>>>>don't let the misinformation fool you. it can be done with php. the
>>>>>>only
>>>>>>thing jerry got right is that it would be a lot of work. what jerry
>>>>>>also
>>>>>>mistakenly forgets is that just about anything you can do with curl,
>>>>>>you
>>>>>>can
>>>>>>do with native php functions...and in this case, the 'just about
>>>>>>anything'
>>>>>>you'd need to be able to do becomes 'anything'. jerry's 'curl could
>>>>>>theoretically' argument then logically negates and invalidates his
>>>>>>'cant
>>>>>>be
>>>>>>done with php' claim.
>>>>>>you're just in for a lot of work. however, it can be done.
>>>>>Hi Guys,
>>>>>I'm not greatly up for a huge deal of work although would be
>>>>>interested in how you would generally start doing it in PHP. However
>>>>>I
>>>>>found another posting on a forum which works and is much easier. Not
>>>>>ideal although we are really only (and i know its aweful) aiming our
>>>>>website at Javascript users.
>>>>as a general and theoretical approach:
>>>>function getResponse($uri, $path, $data, $method = 'POST')
>>>>{
>>>> $method = strtoupper($method);
>>>> $socket = fsockopen($uri, 80);
>>>> if (!$method)){ $method = 'GET'; }
>>>> if (substr($path, 0) != '/'){ $path = '/' . $path; }
>>>> if (!is_array($data)){ $data = array($data); }
>>>> $message = '';
>>>> foreach ($data as $label =$value)
>>>> {
>>>> $message .= '&' . $label . '=' . $value;
>>>> }
>>>> if ($method == 'GET'){ $path .= '?' . $message; }
>>>> fputs($socket, "$method $path http/1.1\r\n");
>>>> fputs($socket, "host: $uri\r\n");
>>>> fputs($socket, "content-type: application/x-www-form-
>>>>urlencoded\r\n");
>>>> fputs($socket, "content-length: " . strlen($message) . "\r\n");
>>>> fputs($socket, "connection: close\r\n\r\n");
>>>> if ($method == 'POST'){ fputs($socket, $message); }
>>>> while (!feof($socket)){ $response .= fgets($socket, 512); }
>>>> fclose($socket);
>>>> return $response;
>>>>}
>>>>$response = getResponse(
>>>> 'www.example.com',
>>>> 'some.page.php' ,
>>>> $_POST ,
>>>> 'POST'
>>>> );
>>>>// parse, validate, process
>>>>effectively, this achieves your html/javascript solution and keeps it
>>>>all
>>>>php.
>>>>that help?
>>>Hi Steve,
>>>Thanks for your detailed response. Would that be able to redirect the
>>>user to the same page as where the data was posted?
>>if you collect information via a page called my.php, put the above code
>>in
>>it. have my.php post to itself. when you get the post, pass the info on
>>to
>>the third party via getResponse...then parse the results...you haven't
>>done
>>any redirecting and the user has used my.php the entire time.
>>>
>>make sense?

Quote:

>>On 14 Dec, 16:22, "Steve" <no....@example.comwrote:
>>>"UKuser" <spiderc...@yahoo.co.ukwrote in message
>>>>
>>>news:6c8d667d-a40b-45c2-bc03-94951dbc137f@i29g2000prf.googlegroups.com...
>>>>
>>>>
>>>>
>>>>On 14 Dec, 15:18, "Steve" <no....@example.comwrote:
>>>>>"UKuser" <spiderc...@yahoo.co.ukwrote in message
>>>>>news:5202d2ed-02a2-407d-87ca-a6a2b50a283c@s8g2000prg.googlegroups.com...
>>>>>>On 14 Dec, 14:42, "Steve" <no....@example.comwrote:
>>>>>>>"UKuser" <spiderc...@yahoo.co.ukwrote in message
>>>>>>>news:6d60314f-61f0-4f08-b1ad-b6cf357cac15@a35g2000prf.googlegroups.com...
>>>>>>>>On 14 Dec, 12:48, Jerry Stuckle <jstuck...@attglobal.netwrote:
>>>>>>>>>UKuser wrote:
>>>>>>>>>>Hi,
>>>>>>>>>>I'm not sure if this can be done as I've searched the web and
>>>>>>>>>>this
>>>>>>>>>>forum.
>>>>>>>>>>I am using an online merchant provider and I must post certain
>>>>>>>>>>variables to their webforms through a form on my website.
>>>>>>>>>>The issue is that I need to gauge whether a user has any items in
>>>>>>>>>>their basket to decide which page I redirect them too. I could
>>>>>>>>>>obviously use cookies or hidden fields etc but these can be
>>>>>>>>>>manipulated.
>>>>>>>>>>How can I force a POST but actually redirect the user as well
>>>>>>>>>>like a
>>>>>>>>>>browser would do? I can do the first part (force the post) as per
>>>>>>>>>>this
>>>>>>>>>>site (the site appears down, so the link uses the Web Archive):
>>>>>>>>>>http://web.archive.org/web/200406282...nd.com/zend/sp...
>>>>>>>>>>Its the second bit if I'm not sure whether it can or can't be
>>>>>>>>>>done.
>>>>>>>>>>If not I'll need to ask the merchant if they allow GET instead.
>>>>>>>>>>Many thanks
>>>>>>>>>>A
>>>>>>>>>Not easy, and it can't be done with PHP. The browser needs to
>>>>>>>>>process
>>>>>>>>>the redirect, so you need to do it from the browser end. That
>>>>>>>>>means a
>>>>>>>>>client-side language such as javascript.
>>>>>>>>>cURL could theoretically help you here - but you're asking for a
>>>>>>>>>lot
>>>>>>>>>of
>>>>>>>>>work, especially if there are several pages being handled after
>>>>>>>>>the
>>>>>>>>>redirect. You'd have to parse each page to see what to do next.
>>>>>>>>>--
>>>>>>>>>==================
>>>>>>>>>Remove the "x" from my email address
>>>>>>>>>Jerry Stuckle
>>>>>>>>>JDS Computer Training Corp.
>>>>>>>>>jstuck...@attglobal.net
>>>>>>>>>==================
>>>>>>>>Thanks for your help. Should have realised because its server side
>>>>>>>>it
>>>>>>>>makes it impossible. Any thoughts on how it could be done with
>>>>>>>>AJAX/JS?
>>>>>>>don't let the misinformation fool you. it can be done with php. the
>>>>>>>only
>>>>>>>thing jerry got right is that it would be a lot of work. what jerry
>>>>>>>also
>>>>>>>mistakenly forgets is that just about anything you can do with curl,
>>>>>>>you
>>>>>>>can
>>>>>>>do with native php functions...and in this case, the 'just about
>>>>>>>anything'
>>>>>>>you'd need to be able to do becomes 'anything'. jerry's 'curl could
>>>>>>>theoretically' argument then logically negates and invalidates his
>>>>>>>'cant
>>>>>>>be
>>>>>>>done with php' claim.
>>>>>>>you're just in for a lot of work. however, it can be done.
>>>>>>Hi Guys,
>>>>>>I'm not greatly up for a huge deal of work although would be
>>>>>>interested in how you would generally start doing it in PHP. However
>>>>>>I
>>>>>>found another posting on a forum which works and is much easier. Not
>>>>>>ideal although we are really only (and i know its aweful) aiming our
>>>>>>website at Javascript users.
>>>>>as a general and theoretical approach:
>>>>>function getResponse($uri, $path, $data, $method = 'POST')
>>>>>{
>>>>> $method = strtoupper($method);
>>>>> $socket = fsockopen($uri, 80);
>>>>> if (!$method)){ $method = 'GET'; }
>>>>> if (substr($path, 0) != '/'){ $path = '/' . $path; }
>>>>> if (!is_array($data)){ $data = array($data); }
>>>>> $message = '';
>>>>> foreach ($data as $label =$value)
>>>>> {
>>>>> $message .= '&' . $label . '=' . $value;
>>>>> }
>>>>> if ($method == 'GET'){ $path .= '?' . $message; }
>>>>> fputs($socket, "$method $path http/1.1\r\n");
>>>>> fputs($socket, "host: $uri\r\n");
>>>>> fputs($socket, "content-type: application/x-www-form-
>>>>>urlencoded\r\n");
>>>>> fputs($socket, "content-length: " . strlen($message) . "\r\n");
>>>>> fputs($socket, "connection: close\r\n\r\n");
>>>>> if ($method == 'POST'){ fputs($socket, $message); }
>>>>> while (!feof($socket)){ $response .= fgets($socket, 512); }
>>>>> fclose($socket);
>>>>> return $response;
>>>>>}
>>>>>$response = getResponse(
>>>>> 'www.example.com',
>>>>> 'some.page.php' ,
>>>>> $_POST ,
>>>>> 'POST'
>>>>> );
>>>>>// parse, validate, process
>>>>>effectively, this achieves your html/javascript solution and keeps it
>>>>>all
>>>>>php.
>>>>>that help?
>>>>Hi Steve,
>>>>Thanks for your detailed response. Would that be able to redirect the
>>>>user to the same page as where the data was posted?
>>>if you collect information via a page called my.php, put the above code
>>>in
>>>it. have my.php post to itself. when you get the post, pass the info on
>>>to
>>>the third party via getResponse...then parse the results...you haven't
>>>done
>>>any redirecting and the user has used my.php the entire time.
>>>>
>>>make sense?
>>Yes it does, unfortunately I have to redirect the user to the page as
>>its a credit card entry form on a completely separate server. They
>>don't appear to accept GET requests only POSTS so I somehow need to
>>get the information and the user to that page.

Quote:

>>>
>> array(
>>>
>> 'var1' ='some content',
>>>
>> 'var2' ='doh'
>>>
>> )
>>>
>>);
>>>
>>$opts = array('http' =>
>>>
>> array(
>>>
>> 'method' ='POST',
>>>
>> 'header' ='Content-type: application/x-www-form-urlencoded',
>>>
>> 'content' =$postdata
>>>
>> )
>>>
>>);
>>>
>>$context = stream_context_create($opts);
>>>
>>$result =
>>file_get_contents('http://localhost/vjezba/post_u_skriptu_2.php', false,
>>$context);
>>>
>>>
>>print_r(explode(' ',$result));

Quote:

>>>$postdata = http_build_query(
>>>>
>>> array(
>>>>
>>> 'var1' ='some content',
>>>>
>>> 'var2' ='doh'
>>>>
>>> )
>>>>
>>>);
>>>>
>>>$opts = array('http' =>
>>>>
>>> array(
>>>>
>>> 'method' ='POST',
>>>>
>>> 'header' ='Content-type: application/x-www-form-urlencoded',
>>>>
>>> 'content' =$postdata
>>>>
>>> )
>>>>
>>>);
>>>>
>>>$context = stream_context_create($opts);
>>>>
>>>$result =
>>>file_get_contents('http://localhost/vjezba/post_u_skriptu_2.php', false,
>>>$context);
>>>>
>>>>
>>>print_r(explode(' ',$result));
>>yes, but jerry seems to think that using this method of putting items in
>>a user's cart on another server is impossible...and that using an html
>>form with the same inputs as is native on the server's checkout form to
>>initiate payment is likewise, impossible. he gets hung up on having to
>>use javascript to do a redirect. php and standard html handle all of that
>>just fine. just don't tell him that.

Quote:

>>>in a user's cart on another server is impossible...and that using an
>>>html form with the same inputs as is native on the server's checkout
>>>form to initiate payment is likewise, impossible. he gets hung up on
>>>having to use javascript to do a redirect. php and standard html handle
>>>all of that just fine. just don't tell him that.

Quote:

>>Again, you claim you can do a redirect with posted values in PHP. Let's
>>see you do it, Steve. The entire world is STILL waiting for you to show
>>us how!

Quote:

Quote:

Quote:

Quote:

>>Nope, I never said you could redirect with post values in cURL. You're
>>the only one who's claimed that can be done. And you still haven't
>>shown how it can be done in PHP. If you have, please show me where.

Quote:

Quote:

>>"Jerry Stuckle" <jstucklex@attglobal.netwrote in message
>>news:_KqdnZ-phoDSWfvanZ2dnUVZ_rCtnZ2d@comcast.com...
>>>
>>>Nope, I never said you could redirect with post values in cURL. You're
>>>the only one who's claimed that can be done. And you still haven't
>>>shown how it can be done in PHP. If you have, please show me where.
>><quote of jerry's initial response to the op>
>>>
>>Not easy, and it can't be done with PHP. The browser needs to process
>>the redirect, so you need to do it from the browser end. That means a
>>client-side language such as javascript.
>>>
>>cURL could theoretically help you here - but you're asking for a lot of
>>work, especially if there are several pages being handled after the
>>redirect. You'd have to parse each page to see what to do next.
>>>
>></quote>
>>>
>>hmmm, you expect the 'it' in "it can't be done with PHP" to mean
>>'redirect', yet think that "curl could theoretically help you here"
>>should somehow be taken in harmony with:
>>>
>><quote>
>>>
>>Nope, I never said you could redirect with post values in cURL.
>>>
>></quote>
>>>
>>what should we read 'here' to mean, as in "theoretically help you here"?
>>i mean, you keep bitching about me showing you to be a liar because i
>>quote you out of context. hell, i just supplied the whole damn post.
>>guess what, kinda makes you seem like you're...well...lying.
>>>

Quote:

Quote:

>>as for the programming shit. why would i suddenly jump out and say, "hey
>>everyone, i'm a programmer"? there's no reason for me to, and in that
>>case ONLY, i'd have to prove the claim. as part of your ad-hom campaign,
>>YOU claimed i was NOT a programmer. YOU have to supply proof. i simply
>>reject your claim because of lack of proof on your part and first-hand
>>knowlege to the contrary. whether i say you're wrong because i have proof
>>to the contrary or not, your claim is simply rejected because you have no
>>supporing evidence.
>>>

Quote:

Quote:

Quote:

Quote:

>>Steve wrote:
>>>"Jerry Stuckle" <jstucklex@attglobal.netwrote in message
>>>news:_KqdnZ-phoDSWfvanZ2dnUVZ_rCtnZ2d@comcast.com...
>>>>
>>>>Nope, I never said you could redirect with post values in cURL.
>>>>You're the only one who's claimed that can be done. And you still
>>>>haven't shown how it can be done in PHP. If you have, please show me
>>>>where.
>>><quote of jerry's initial response to the op>
>>>>
>>>Not easy, and it can't be done with PHP. The browser needs to process
>>>the redirect, so you need to do it from the browser end. That means a
>>>client-side language such as javascript.
>>>>
>>>cURL could theoretically help you here - but you're asking for a lot of
>>>work, especially if there are several pages being handled after the
>>>redirect. You'd have to parse each page to see what to do next.
>>>>
>>></quote>
>>>>
>>>hmmm, you expect the 'it' in "it can't be done with PHP" to mean
>>>'redirect', yet think that "curl could theoretically help you here"
>>>should somehow be taken in harmony with:
>>>>
>>><quote>
>>>>
>>>Nope, I never said you could redirect with post values in cURL.
>>>>
>>></quote>
>>>>
>>>what should we read 'here' to mean, as in "theoretically help you
>>>here"? i mean, you keep bitching about me showing you to be a liar
>>>because i quote you out of context. hell, i just supplied the whole
>>>damn post. guess what, kinda makes you seem like you're...well...lying.
>>>>
>>You really don't know how to read, do you, Stevie. I said it couldn't
>>be done in PHP. And that is correct. Period.
>>>
>>Then I went on to say that cURL could help him. But I didn't say cURL
>>could do the redirect.

Quote:

>>You're the only one who has claimed PHP can do redirects.

Quote:

>>>as for the programming shit. why would i suddenly jump out and say,
>>>"hey everyone, i'm a programmer"? there's no reason for me to, and in
>>>that case ONLY, i'd have to prove the claim. as part of your ad-hom
>>>campaign, YOU claimed i was NOT a programmer. YOU have to supply proof.
>>>i simply reject your claim because of lack of proof on your part and
>>>first-hand knowlege to the contrary. whether i say you're wrong because
>>>i have proof to the contrary or not, your claim is simply rejected
>>>because you have no supporing evidence.
>>>>
>>You're desperately looking for acceptance from someone, some where.

>>And nope, you're the one who claimed you are a programmer. Prove it.
>>But you can't, loser.

Quote:

>>"Jerry Stuckle" <jstucklex@attglobal.netwrote in message
>>news:toudnehNdoqSIe7anZ2dnUVZ_jWdnZ2d@comcast.co m...
>>>Steve wrote:
>>>>"Jerry Stuckle" <jstucklex@attglobal.netwrote in message
>>>>news:_KqdnZ-phoDSWfvanZ2dnUVZ_rCtnZ2d@comcast.com...
>>>>>
>>>>>Nope, I never said you could redirect with post values in cURL.
>>>>>You're the only one who's claimed that can be done. And you still
>>>>>haven't shown how it can be done in PHP. If you have, please show me
>>>>>where.
>>>><quote of jerry's initial response to the op>
>>>>>
>>>>Not easy, and it can't be done with PHP. The browser needs to process
>>>>the redirect, so you need to do it from the browser end. That means a
>>>>client-side language such as javascript.
>>>>>
>>>>cURL could theoretically help you here - but you're asking for a lot of
>>>>work, especially if there are several pages being handled after the
>>>>redirect. You'd have to parse each page to see what to do next.
>>>>>
>>>></quote>
>>>>>
>>>>hmmm, you expect the 'it' in "it can't be done with PHP" to mean
>>>>'redirect', yet think that "curl could theoretically help you here"
>>>>should somehow be taken in harmony with:
>>>>>
>>>><quote>
>>>>>
>>>>Nope, I never said you could redirect with post values in cURL.
>>>>>
>>>></quote>
>>>>>
>>>>what should we read 'here' to mean, as in "theoretically help you
>>>>here"? i mean, you keep bitching about me showing you to be a liar
>>>>because i quote you out of context. hell, i just supplied the whole
>>>>damn post. guess what, kinda makes you seem like you're...well...lying.
>>>>>
>>>You really don't know how to read, do you, Stevie. I said it couldn't
>>>be done in PHP. And that is correct. Period.
>>>>
>>>Then I went on to say that cURL could help him. But I didn't say cURL
>>>could do the redirect.
>>you said it could 'theoretically' be done using curl.
>>>

Quote:

>>>You're the only one who has claimed PHP can do redirects.
>>nope, i said he could use just php and html to get the desired results.
>>you need help with *your* reading.
>>>

Quote:

Quote:

>>>>as for the programming shit. why would i suddenly jump out and say,
>>>>"hey everyone, i'm a programmer"? there's no reason for me to, and in
>>>>that case ONLY, i'd have to prove the claim. as part of your ad-hom
>>>>campaign, YOU claimed i was NOT a programmer. YOU have to supply proof.
>>>>i simply reject your claim because of lack of proof on your part and
>>>>first-hand knowlege to the contrary. whether i say you're wrong because
>>>>i have proof to the contrary or not, your claim is simply rejected
>>>>because you have no supporing evidence.
>>>>>
>>>You're desperately looking for acceptance from someone, some where.
>>really? lol.
>>>
>>>And nope, you're the one who claimed you are a programmer. Prove it.
>>>But you can't, loser.
>>idiot. you said i was not a programmer. it's up to *you* to prove it. i
>>and my employers know otherwise.
>>>

Quote:

>>Steve wrote:
>>>"Jerry Stuckle" <jstucklex@attglobal.netwrote in message
>>>news:toudnehNdoqSIe7anZ2dnUVZ_jWdnZ2d@comcast.c om...
>>>>Steve wrote:
>>>>>"Jerry Stuckle" <jstucklex@attglobal.netwrote in message
>>>>>news:_KqdnZ-phoDSWfvanZ2dnUVZ_rCtnZ2d@comcast.com...
>>>>>>
>>>>>>Nope, I never said you could redirect with post values in cURL.
>>>>>>You're the only one who's claimed that can be done. And you still
>>>>>>haven't shown how it can be done in PHP. If you have, please show
>>>>>>me where.
>>>>><quote of jerry's initial response to the op>
>>>>>>
>>>>>Not easy, and it can't be done with PHP. The browser needs to
>>>>>process
>>>>>the redirect, so you need to do it from the browser end. That means
>>>>>a
>>>>>client-side language such as javascript.
>>>>>>
>>>>>cURL could theoretically help you here - but you're asking for a lot
>>>>>of
>>>>>work, especially if there are several pages being handled after the
>>>>>redirect. You'd have to parse each page to see what to do next.
>>>>>>
>>>>></quote>
>>>>>>
>>>>>hmmm, you expect the 'it' in "it can't be done with PHP" to mean
>>>>>'redirect', yet think that "curl could theoretically help you here"
>>>>>should somehow be taken in harmony with:
>>>>>>
>>>>><quote>
>>>>>>
>>>>>Nope, I never said you could redirect with post values in cURL.
>>>>>>
>>>>></quote>
>>>>>>
>>>>>what should we read 'here' to mean, as in "theoretically help you
>>>>>here"? i mean, you keep bitching about me showing you to be a liar
>>>>>because i quote you out of context. hell, i just supplied the whole
>>>>>damn post. guess what, kinda makes you seem like
>>>>>you're...well...lying.
>>>>>>
>>>>You really don't know how to read, do you, Stevie. I said it couldn't
>>>>be done in PHP. And that is correct. Period.
>>>>>
>>>>Then I went on to say that cURL could help him. But I didn't say cURL
>>>>could do the redirect.
>>>you said it could 'theoretically' be done using curl.
>>>>
>>Read again, stoopid. I said no such thing.

>>>>You're the only one who has claimed PHP can do redirects.
>>>nope, i said he could use just php and html to get the desired results.
>>>you need help with *your* reading.
>>>>
>>No, you claimed PHP could do redirects. Now you're backpedaling.

>>Keep it up, stoopid troll.

>>>>>as for the programming shit. why would i suddenly jump out and say,
>>>>>"hey everyone, i'm a programmer"? there's no reason for me to, and in
>>>>>that case ONLY, i'd have to prove the claim. as part of your ad-hom
>>>>>campaign, YOU claimed i was NOT a programmer. YOU have to supply
>>>>>proof. i simply reject your claim because of lack of proof on your
>>>>>part and first-hand knowlege to the contrary. whether i say you're
>>>>>wrong because i have proof to the contrary or not, your claim is
>>>>>simply rejected because you have no supporing evidence.
>>>>>>
>>>>You're desperately looking for acceptance from someone, some where.
>>>really? lol.
>>>>
>>>>And nope, you're the one who claimed you are a programmer. Prove it.
>>>>But you can't, loser.
>>>idiot. you said i was not a programmer. it's up to *you* to prove it. i
>>>and my employers know otherwise.
>>>>
>>Yea, right. You claim you are a programmer. I challenged your claim.
>>Prove it, stoopid.

Quote:

>>"Jerry Stuckle" <jstucklex@attglobal.netwrote in message
>>news:V9idnd-ZVKMpzOXanZ2dnUVZ_qPinZ2d@comcast.com...
>>>Steve wrote:
>>>>"Jerry Stuckle" <jstucklex@attglobal.netwrote in message
>>>>news:toudnehNdoqSIe7anZ2dnUVZ_jWdnZ2d@comcast. com...
>>>>>Steve wrote:
>>>>>>"Jerry Stuckle" <jstucklex@attglobal.netwrote in message
>>>>>>news:_KqdnZ-phoDSWfvanZ2dnUVZ_rCtnZ2d@comcast.com...
>>>>>>>
>>>>>>>Nope, I never said you could redirect with post values in cURL.
>>>>>>>You're the only one who's claimed that can be done. And you still
>>>>>>>haven't shown how it can be done in PHP. If you have, please show
>>>>>>>me where.
>>>>>><quote of jerry's initial response to the op>
>>>>>>>
>>>>>>Not easy, and it can't be done with PHP. The browser needs to
>>>>>>process
>>>>>>the redirect, so you need to do it from the browser end. That means
>>>>>>a
>>>>>>client-side language such as javascript.
>>>>>>>
>>>>>>cURL could theoretically help you here - but you're asking for a lot
>>>>>>of
>>>>>>work, especially if there are several pages being handled after the
>>>>>>redirect. You'd have to parse each page to see what to do next.
>>>>>>>
>>>>>></quote>
>>>>>>>
>>>>>>hmmm, you expect the 'it' in "it can't be done with PHP" to mean
>>>>>>'redirect', yet think that "curl could theoretically help you here"
>>>>>>should somehow be taken in harmony with:
>>>>>>>
>>>>>><quote>
>>>>>>>
>>>>>>Nope, I never said you could redirect with post values in cURL.
>>>>>>>
>>>>>></quote>
>>>>>>>
>>>>>>what should we read 'here' to mean, as in "theoretically help you
>>>>>>here"? i mean, you keep bitching about me showing you to be a liar
>>>>>>because i quote you out of context. hell, i just supplied the whole
>>>>>>damn post. guess what, kinda makes you seem like
>>>>>>you're...well...lying.
>>>>>>>
>>>>>You really don't know how to read, do you, Stevie. I said it couldn't
>>>>>be done in PHP. And that is correct. Period.
>>>>>>
>>>>>Then I went on to say that cURL could help him. But I didn't say cURL
>>>>>could do the redirect.
>>>>you said it could 'theoretically' be done using curl.
>>>>>
>>>Read again, stoopid. I said no such thing.
>>>
>>already addressed that with quotes and message id's. can't help that you
>>can't read.
>>>
>>>>>You're the only one who has claimed PHP can do redirects.
>>>>nope, i said he could use just php and html to get the desired results.
>>>>you need help with *your* reading.
>>>>>
>>>No, you claimed PHP could do redirects. Now you're backpedaling.
>>nope...read again...then post the claim, i.e. quote me.
>>>
>>>Keep it up, stoopid troll.
>>yes, do.
>>>
>>>>>>as for the programming shit. why would i suddenly jump out and say,
>>>>>>"hey everyone, i'm a programmer"? there's no reason for me to, and in
>>>>>>that case ONLY, i'd have to prove the claim. as part of your ad-hom
>>>>>>campaign, YOU claimed i was NOT a programmer. YOU have to supply
>>>>>>proof. i simply reject your claim because of lack of proof on your
>>>>>>part and first-hand knowlege to the contrary. whether i say you're
>>>>>>wrong because i have proof to the contrary or not, your claim is
>>>>>>simply rejected because you have no supporing evidence.
>>>>>>>
>>>>>You're desperately looking for acceptance from someone, some where.
>>>>really? lol.
>>>>>
>>>>>And nope, you're the one who claimed you are a programmer. Prove it.
>>>>>But you can't, loser.
>>>>idiot. you said i was not a programmer. it's up to *you* to prove it. i
>>>>and my employers know otherwise.
>>>>>
>>>Yea, right. You claim you are a programmer. I challenged your claim.
>>>Prove it, stoopid.
>>already addressed this with quotes and message id's. post my original
>>'claim', i.e. quote me.
>>>

Quote:

Quote: