SoapClient can't parse WSDL file correctly

[TheOneThingSpecial]

Description

The following code:

<?php
function testsoap()
{
    try {
        $client = new SoapClient('tmp.txt'); 
        $res = $client->__getFunctions();
        var_dump($res);
    } catch (Exception $e) {
        var_dump($e->getMessage());
    }
}

testsoap();

tmp.txt:
tmp.txt

Resulted in this output:

But I expected this output instead:

Test:
When I modify the source file ext/soap/php_sdl.c and add debugging information, as shown below：

I got the result as below:

So I think there might be a problem with this line
ctype = strrchr((char*)type->children->content,':');

PHP Version

PHP 7.3.24

Operating System

Centos 6.10

[damianwadley]

<wsdl:portType name="http://wssmcommupper/">

This is quite clearly incorrect.

[TheOneThingSpecial]

I can correctly parse the WSDL file with soapUI tool, so I think PHP may not handle it correctly！

[damianwadley]

I can correctly parse the WSDL file with soapUI tool, so I think PHP may not handle it correctly！

The WSDL itself is not correct because the name of that type is not valid. If some other tool doesn't care then that's nice.

But I don't have the desire to try to explain that any more.

[cmb69]

Please don't post screenshots if the text can easily copy&pasted into the ticket.

[cmb69]

<wsdl:portType name="http://wssmcommupper/">

This is quite clearly incorrect.

Right, it needs to be an nmtoken. However, I think that <wsdl:portType name="http:wssmcommupper"> would be correct (well, let's say allowed), but that results in the same behavior.

So I think there might be a problem with this line
ctype = strrchr((char*)type->children->content,':');

I concur. Just looking for the rightmost colon doesn't look right. From what I can tell, this line is supposed to strip the namespace prefix, which is not allowed to contain any colons, so using strchr() instead of strrchr() appears to be the correct solution.

[cmb69]

PHP 7.3.24

PHP-7.3 is no longer actively supported; that doesn't matter wrt. this ticket, since the relevant code hasn't changed, but you want to update to any of the supported versions anyway.