php.net |  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login

go to bug id or search bugs for

Bug #10572 https takes forever and a day when curl is enabled
Submitted: 2001-05-01 02:13 UTC Modified: 2001-05-02 15:33 UTC
From: Clement dot Ong at shinetech dot com Assigned:
Status: Closed Package: cURL related
PHP Version: 4.0.5 OS: Linux Red Hat 7.0
Private report: No CVE-ID: None
View Developer Edit
Welcome back! If you're the original bug submitter, here's where you can edit the bug or add additional notes.
If you forgot your password, you can retrieve your password here.
Password:
Status:
Package:
Bug Type:
Summary:
From: Clement dot Ong at shinetech dot com
New email:
PHP Version: OS:

 

 [2001-05-01 02:13 UTC] Clement dot Ong at shinetech dot com 
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

Patches

Pull Requests

History

AllCommentsChangesGit/SVN commitsRelated reports
 [2001-05-01 08:55 UTC] jmoore@php.net 
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 21:47 UTC] Clement dot Ong at shinetech dot com 
 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.
 [2001-05-02 00:24 UTC] Clement dot Ong at shinetech dot com 
I managed to get https working with curl by copying libcurl.so.2.0.0 from my server that works.

Here is the output of running ldd on both versions :-

#ldd libcurl.so.2.0.0.working
        libdl.so.2 => /lib/libdl.so.2 (0x400c9000)
        libc.so.6 => /lib/libc.so.6 (0x400cc000)
        /lib/ld-linux.so.2 => /lib/ld-linux.so.2 0x80000000)

#ldd libcurl.so.2.0.0
        libssl.so.0 => /usr/lib/libssl.so.0 (0x4001f000)
        libcrypto.so.0 => /usr/lib/libcrypto.so.0 (0x4004d000)
        libdl.so.2 => /lib/libdl.so.2 (0x40105000)
        libc.so.6 => /lib/libc.so.6 (0x40108000)
        /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x80000000)

For whatever reason CURL on the new server is not using shared objects for libssl.so and libcrypto.so as evidence by them missing and the file size being about 4 times larger than the working version.

For you info I used the following command to build CURL 7.7.1
./configure --with-ssl-

It appears that this is not a PHP problem.
 [2001-05-02 15:33 UTC] sterling@php.net 
user said: not a php problem, therefore bug closed, please
file it with the cURL folks (http://curl.haxx.se)..
 
PHP Copyright © 2001-2024 The PHP Group
All rights reserved. 		Last updated: Fri Dec 27 14:01:29 2024 UTC