It's time I "fessed up" -- I've found the solution to my problem.

And no, it wasn't anything to do with cURL, or the cURL-PHP binding.

I was onto something when I asked about a transfer limit. There is by
default a limit to the length of ERROR MESSAGES that PHP will print to
the error log, which had conveniently slipped my mind. So in fact I was
getting the entire response. I just wasn't seeing it when I printed it
to the error log.

How obvious these things can seem once you've figured them out.

On to Brian's message:

On Sat, 5 Feb 2005, Brian Wilkins said:
> I don't get the response from the webserver that way. It works much
> better like this:

<snip example of using CURLOPT_WRITEFUNCTION>

I like that, but I'm not sure what gets you over the
CURLOPT_RETURNTRANSFER method. What's your rationale for using this
method instead?

Michael
Received on 2005-02-06