CV>> Sterling has been fixing some other cURL stuff, but he's told me
CV>> (offlist) that he can't look at this problem until next week.
CV>> Hopefully someone else can stand up and take a quick look.
Could you please try the attached patch? It seems to me that it results in
a sane behaviour, whi
CV>> Sterling has been fixing some other cURL stuff, but he's told me
CV>> (offlist) that he can't look at this problem until next week.
CV>> Hopefully someone else can stand up and take a quick look.
Generally, I think I know how to fix this in PHP. I am not copletely sure,
however, that cURL's
CV>> I reported this already: bug #12018
CV>>
CV>> Sterling has been fixing some other cURL stuff, but he's told me (offlist)
CV>> that he can't look at this problem until next week. Hopefully someone else
CV>> can stand up and take a quick look.
Seems that I know what is the problem - header ha
> Seems like recent cURL module always outputs the header to STDOUT, even if
> the curl_setopt ($c, CURLOPT_HEADER, 0) was called. I do not know if it's
> cURL library or PHP cURL module problem, but obviously it is going to
> break a lot of scripts this way.
I reported this already: bug #12018
Seems like recent cURL module always outputs the header to STDOUT, even if
the curl_setopt ($c, CURLOPT_HEADER, 0) was called. I do not know if it's
cURL library or PHP cURL module problem, but obviously it is going to
break a lot of scripts this way.
--
Stanislav Malyshev, Zend Products Enginee
