ID: 10572
User Update by: [EMAIL PROTECTED]
Old-Status: Feedback
Status: Open
Bug Type: cURL related
Description: https takes forever and a day when curl is enabled

 This is the confuration I use on build 200104091745

./configure --with-apxs=/usr/local/apache/bin/apxs \
--with-config-file-path=/etc/php \
--with-mysql=/usr \
--with-java=/usr/java/jdk1.3 \
--with-ldap \
--with-imap \
--with-curl \
--with-gd \
--enable-versioning

the URL I use is https://www.shinemail.com which is an internal resource.



Previous Comments:
---------------------------------------------------------------------------

[2001-05-01 08:55:30] [EMAIL PROTECTED]
Can you please provide a small simple script to reproduce this (so that we can use it) 
also your configure line would be useful.

- James

---------------------------------------------------------------------------

[2001-05-01 02:13:02] [EMAIL PROTECTED]
I am experiencing the same problem(https takes a long time to return when curl is 
enabled with php) as noted in 

    http://www.php.net/bugs.php?id=10195

after I built our production machine. All the software components and their versions 
are the same on both machines.

When I did a uname on the server that is working with https and curl enabled I get 

localhost.localdomain 2.2.16-22 #1 Tue Aug 22 16:16:55 EDT 2000 i586 unknown

on the server that is not working it is :-

localhost.localdomain 2.2.16-22 #1 Tue Aug 22 16:17:40 EDT 2000 i686 unknown

Could the differerent instruction set be causing the problem, i686 compared to i586?

I've downloaded the latest build(April 30th) but the make fails with problems with 
curl headers.

Does anyone know what is this happening?

cheers,

Clement







---------------------------------------------------------------------------


Full Bug description available at: http://bugs.php.net/?id=10572


-- 
PHP Development Mailing List <http://www.php.net/>
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]

Reply via email to