General SOAP weirdness... libxml default stream context?

[Rik Wasmus]

I had some problems on 1 particular server (up to 3 others with the same
PHP&SOAP version work, 1 of which with the same OS) with constructing a
SOAP client:

FAIL:
<?php
ini_set('soap.wsdl_cache_enabled',0);
$client = new SOAPClient('https://example.com/?WSDL');
?>
Error:
Fatal error: Uncaught SoapFault exception: [WSDL] SOAP-ERROR: Parsing
WSDL: Couldn't load from 'https://....

SUCCESS:
<?php
ini_set('soap.wsdl_cache_enabled',0);
$ctx = stream_context_create();
libxml_set_streams_context($ctx);
$client = new SOAPClient('https://example.com/?WSDL');
?>

.... and it allready works, and I was planning to add all kinds of notifies
on stream alterations, disabling verify_peer (allthough the certificate is
valid..), etc. Nothing like that needed, just adding _some_ context
allready did the trick... I'm suitably amazed, any idea why this is? An
overriding of a buggy default context perhaps?

And some further digging, this was all that's needed:
<?php
ini_set('soap.wsdl_cache_enabled',0);
$client = new SOAPClient('https://example.com?WSDL',
array('stream_context'=stream_context_create()));
?>

Call me amazed. Ah well, the last server works too now...
--
Rik Wasmus
....spamrun finished

[Curtis]

Rik Wasmus wrote:

I had some problems on 1 particular server (up to 3 others with the same
PHP&SOAP version work, 1 of which with the same OS) with constructing a
SOAP client:

FAIL:
<?php
ini_set('soap.wsdl_cache_enabled',0);
$client = new SOAPClient('https://example.com/?WSDL');
?>
Error:
Fatal error: Uncaught SoapFault exception: [WSDL] SOAP-ERROR: Parsing
WSDL: Couldn't load from 'https://....

SUCCESS:
<?php
ini_set('soap.wsdl_cache_enabled',0);
$ctx = stream_context_create();
libxml_set_streams_context($ctx);
$client = new SOAPClient('https://example.com/?WSDL');
?>

... and it allready works, and I was planning to add all kinds of
notifies on stream alterations, disabling verify_peer (allthough the
certificate is valid..), etc. Nothing like that needed, just adding
_some_ context allready did the trick... I'm suitably amazed, any idea
why this is? An overriding of a buggy default context perhaps?

And some further digging, this was all that's needed:
<?php
ini_set('soap.wsdl_cache_enabled',0);
$client = new SOAPClient('https://example.com?WSDL',
array('stream_context'=stream_context_create()));
?>

Call me amazed. Ah well, the last server works too now...
--Rik Wasmus
...spamrun finished

Hey Rik:

I think it may be a bug. I pasted your error in Google and found these
two bug reports:

<URL:http://bugs.php.net/bug.php?id=34657>
<URL:http://bugs.php.net/bug.php?id=38703>

I'm not sure if this will shed light on your particular case, but hope
it helps.

--
Curtis

[Rik Wasmus]

On Wed, 04 Jun 2008 22:28:40 +0200, Curtis <ze******@verizon.netwrote:

Rik Wasmus wrote:

>I had some problems on 1 particular server (up to 3 others with the
same PHP&SOAP version work, 1 of which with the same OS) with
constructing a SOAP client:
FAIL:
<?php
ini_set('soap.wsdl_cache_enabled',0);
$client = new SOAPClient('https://example.com/?WSDL');
?>
Error:
Fatal error: Uncaught SoapFault exception: [WSDL] SOAP-ERROR: Parsing
WSDL: Couldn't load from 'https://....
SUCCESS:
<?php
ini_set('soap.wsdl_cache_enabled',0);
$ctx = stream_context_create();
libxml_set_streams_context($ctx);
$client = new SOAPClient('https://example.com/?WSDL');
?>
... and it allready works, and I was planning to add all kinds of
notifies on stream alterations, disabling verify_peer (allthough the
certificate is valid..), etc. Nothing like that needed, just adding
_some_ context allready did the trick... I'm suitably amazed, any idea
why this is? An overriding of a buggy default context perhaps?
And some further digging, this was all that's needed:
<?php
ini_set('soap.wsdl_cache_enabled',0);
$client = new SOAPClient('https://example.com?WSDL',
array('stream_context'=stream_context_create()));
?>
Call me amazed. Ah well, the last server works too now...

I think it may be a bug. I pasted your error in Google and found these
two bug reports:

<URL:http://bugs.php.net/bug.php?id=34657>

Well, yes, it is the error, but not related: that's about it issuing a
Fatal Error rather then a catchable Exception on a fail. (An issue still
current when someone has XDebug installed however, I think XDebug needs to
fix that, I assume it's not SOAP's fault). The reason for the error there
is not the problem, the ability to catch it is.

<URL:http://bugs.php.net/bug.php?id=38703>

Is sort of about the same thing.

I'm not sure if this will shed light on your particular case, but hope
it helps.

Unfortunately, no, the issuing of the error is not of importance to me,
the reason for it is, and the reason why an empty context fixes it. If
only an empty context didn't fix it, I could easily trace the SoapClient
constructor beneath the surface... For now, it would be stepping throughC
code, not something I am about to do :) But thank you for thinking along,
much appreciated.

As it seems not to depend on a PHP version / OS / Soap settings, I suspect
it would either be a result of unknown settings (which I can't figure
out), or a rather unique combination of PHP version / OS / libraries. Not
reportable as a bug as of yet, just a big mystery.

Ah, well, what am I whining about, the issue is fixed, but I hate fixes I
don't understand :)
--
Rik Wasmus
....spamrun finished

[Curtis]

Rik Wasmus wrote:

On Wed, 04 Jun 2008 22:28:40 +0200, Curtis <ze******@verizon.netwrote:

>Rik Wasmus wrote:

>>I had some problems on 1 particular server (up to 3 others with the
same PHP&SOAP version work, 1 of which with the same OS) with
constructing a SOAP client:
FAIL:
<?php
ini_set('soap.wsdl_cache_enabled',0);
$client = new SOAPClient('https://example.com/?WSDL');
?>
Error:
Fatal error: Uncaught SoapFault exception: [WSDL] SOAP-ERROR: Parsing
WSDL: Couldn't load from 'https://....
SUCCESS:
<?php
ini_set('soap.wsdl_cache_enabled',0);
$ctx = stream_context_create();
libxml_set_streams_context($ctx);
$client = new SOAPClient('https://example.com/?WSDL');
?>
... and it allready works, and I was planning to add all kinds of
notifies on stream alterations, disabling verify_peer (allthough the
certificate is valid..), etc. Nothing like that needed, just adding
_some_ context allready did the trick... I'm suitably amazed, any
idea why this is? An overriding of a buggy default context perhaps?
And some further digging, this was all that's needed:
<?php
ini_set('soap.wsdl_cache_enabled',0);
$client = new SOAPClient('https://example.com?WSDL',
array('stream_context'=stream_context_create()));
?>
Call me amazed. Ah well, the last server works too now...

I think it may be a bug. I pasted your error in Google and found these
two bug reports:

<URL:http://bugs.php.net/bug.php?id=34657>

Well, yes, it is the error, but not related: that's about it issuing a
Fatal Error rather then a catchable Exception on a fail. (An issue still
current when someone has XDebug installed however, I think XDebug needs
to fix that, I assume it's not SOAP's fault). The reason for the error
there is not the problem, the ability to catch it is.

><URL:http://bugs.php.net/bug.php?id=38703>

Is sort of about the same thing.

Ah, ok. I wasn't too sure if it was directly pertinent.

>I'm not sure if this will shed light on your particular case, but hope
it helps.

Unfortunately, no, the issuing of the error is not of importance to me,
the reason for it is, and the reason why an empty context fixes it. If
only an empty context didn't fix it, I could easily trace the SoapClient
constructor beneath the surface... For now, it would be stepping through
C code, not something I am about to do :) But thank you for thinking
along, much appreciated.

Thanks for putting this out there, you might save plenty of others
some trouble with your workaround.

As it seems not to depend on a PHP version / OS / Soap settings, I
suspect it would either be a result of unknown settings (which I can't
figure out), or a rather unique combination of PHP version / OS /
libraries. Not reportable as a bug as of yet, just a big mystery.

If you think it might be relevant as a user note on PHP's docs, maybe
post one there (if you haven't already).

Ah, well, what am I whining about, the issue is fixed, but I hate fixes
I don't understand :)

Lol. If it's any consolation, I feel the same way. :P

--
Curtis