On Mon, 25 Nov 2002, John Clendinen wrote:

> But when we simulate that same form posting using cURL, the PHP script
> containing the cURL execute is timing out.

Doing a single simple POST to a https site? What curl version, what php
version on which operating system?

> So, logically, I tried connecting to the same page using cURL from the
> command line, and it seems to establish a socket but then just sits there.
> Never closes the connection until I break it. This too is useless.

If curl can't do it from the command line, then don't expect it to do it
correct from within PHP.

I'd recommend getting the command line version to work first.

Could you perhaps show us how such a command line looks like? How much date
does curl receive or doesn't it receive anything at all?

> Some more info: The URI to which cURL is connecting (or supposed to be
> connecting) is secure, https, port 443. If I run the same PHP script
> mentioned above but specify non-secure port 80, I get plenty of response --
> the standard forbidden/rejection response. I get a similar reaction if I
> try to open a socket -- whether port 443 or port 80 -- using fsockopen(),
> fputs, and fgets.

Well, the port number surely doesn't matter, the protocol does. HTTP can be
spoken on 80 or 443 if you want to, and so can HTTPS. But usually we keep
HTTP on 80 and HTTPS on 443. When you do "fsockopen" on 443, that's like
putting curl to speak HTTP on 443.

If that works, it would seem like the site doesn't run SSL on that port.

> Naturally, when I call A.net on the phone for support, they seem annoyed
> and assure me it's not their problem.

Nothing beats a friendly staff! ;-(

-- 
 Daniel Stenberg -- curl, cURL, Curl, CURL. Groks URLs.
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf