Hi all,
we've bumped into a possible bug where file_get_contents() returns empty
string if we try to get contents from HTTPS source. This error only occurs
if PHP is compiled with --with-curlwrappers.
Funny thing is this only happens on slackware 13.1, but not on 13.0 or
older. I've checked ./configure and make output and they are almost
identical, strace does not return anything meaningful.
Environment is highly controlled by configuration management, software is
built in the same way, except underlying OS versions (and very basic libs
and tools versions) differ.
Two questions:
- Do any of you guys have any idea about this?
- How to continue exploring deeper to discover what actually this error is
all about?
Regards,
b.
Hi all,
we've bumped into a possible bug where
file_get_contents()returns empty
string if we try to get contents from HTTPS source. This error only occurs
if PHP is compiled with --with-curlwrappers.Funny thing is this only happens on slackware 13.1, but not on 13.0 or
older. I've checked ./configure and make output and they are almost
identical, strace does not return anything meaningful.
Environment is highly controlled by configuration management, software is
built in the same way, except underlying OS versions (and very basic libs
and tools versions) differ.Two questions:
- Do any of you guys have any idea about this?
- How to continue exploring deeper to discover what actually this error is
all about?Regards,
b.
Have you checked it's not a failure verificating the certificate?
Hi all,
we've bumped into a possible bug where
file_get_contents()returns empty
string if we try to get contents from HTTPS source. This error only occurs
if PHP is compiled with --with-curlwrappers.Funny thing is this only happens on slackware 13.1, but not on 13.0 or
older. I've checked ./configure and make output and they are almost
identical, strace does not return anything meaningful.
Environment is highly controlled by configuration management, software is
built in the same way, except underlying OS versions (and very basic libs
and tools versions) differ.Two questions:
- Do any of you guys have any idea about this?
- How to continue exploring deeper to discover what actually this error is
all about?
Does a command line curl call to the same SSL URL work?
-Rasmus
Weird. Curl is consistent. It does not work (in this case) without -k
(--insecure) option or explicitly setting ca-bundle on all OS versions.
Thanks for pointers, will remove --with-curlwrappers (marked experimental)
from my PHP configure line.
BTW what is the plan with --with-curlwrappers?
Will this eventually replace current stream code as default wrapper for
communication over the net?
Thanks,
b.
Hi all,
we've bumped into a possible bug where
file_get_contents()returns empty
string if we try to get contents from HTTPS source. This error only
occurs
if PHP is compiled with --with-curlwrappers.Funny thing is this only happens on slackware 13.1, but not on 13.0 or
older. I've checked ./configure and make output and they are almost
identical, strace does not return anything meaningful.
Environment is highly controlled by configuration management, software is
built in the same way, except underlying OS versions (and very basic libs
and tools versions) differ.Two questions:
- Do any of you guys have any idea about this?
- How to continue exploring deeper to discover what actually this error
is
all about?Does a command line curl call to the same SSL URL work?
-Rasmus