Thee is a PEAR package to do posts, gets, etc.
http://pear.php.net/package/HTTP_Request
On Fri, 16 Jul 2004 14:00:02 -0700, Vail, Warren <[EMAIL PROTECTED]> wrote:
> I believe we all missed something important here, but I've been wrong
> before.
>
> Notice his URL below, specifically the "https"
The client's vendor only specifies that it's = pairs and
that it's URL encoded so I don't think that's an issue. But don't let
that squelch any discussion. :)
Jeff Oien
Vail, Warren wrote:
I believe we all missed something important here, but I've been wrong
before.
Notice his URL below, specifi
I believe we all missed something important here, but I've been wrong
before.
Notice his URL below, specifically the "https" part.
I believe this means that the data not only needs to be URL encoded but SSL
encrypted. I believe this makes a stronger case for using CURL, does it
not? I also woul
Jeff Oien wrote:
Thanks for the helpful examples. One other question. Is there an
advantage to sending the URL via a header as opposed to doing http_post
like this?
http://shiflett.org/hacks/php/http_post
Jeff
As mentioned a couple of times, size is one. But you still need to
url-encode the data
]
Sent: Friday, July 16, 2004 1:12 PM
To: PHP
Subject: Re: [PHP] Re: Putting $_POST into string to send to ASP
Thanks for the helpful examples. One other question. Is there an
advantage to sending the URL via a header as opposed to doing http_post
like this?
http://shiflett.org/hacks/php/http_post
> Thanks for the helpful examples. One other question. Is there an
> advantage to sending the URL via a header as opposed to doing http_post
> like this?
> http://shiflett.org/hacks/php/http_post
> Jeff
Like someone mentioned earlier. URL's have length limits. That would
be one reason to do a po
16, 2004 12:55 PM
> To: Vail, Warren
> Cc: 'Lars Torben Wilson'; Jeff Oien; PHP
> Subject: Re: [PHP] Re: Putting $_POST into string to send to ASP
>
>
> Vail, Warren wrote:
>
> > How about (probably one of fifty solutions;
> >
> > Foreach($_POST as
Thanks for the helpful examples. One other question. Is there an
advantage to sending the URL via a header as opposed to doing http_post
like this?
http://shiflett.org/hacks/php/http_post
Jeff
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
Vail, Warren wrote:
How about (probably one of fifty solutions;
Foreach($_POST as $k => $v) $vals[] = $k."=".$v;
$strvals = urlencode(implode("&",$vals));
Header("Location: https://example.com/script.asp?".$strvals);
One thing to think about, URL's are limited in length, and one reason for
using me
How about (probably one of fifty solutions;
Foreach($_POST as $k => $v) $vals[] = $k."=".$v;
$strvals = urlencode(implode("&",$vals));
Header("Location: https://example.com/script.asp?".$strvals);
One thing to think about, URL's are limited in length, and one reason for
using method=post is that
10 matches
Mail list logo
