SOAP fault due to "SOAP-ERROR: Parsing Schema: can't import schema from 'http://schemas.xmlsoap.org/soap/encoding/' " about magento-lts HOT 25 CLOSED

Confirm, problem started a few days ago. Sometimes it works, sometimes it doesn't.
I try to solve it via DNS and locally served xml(no success yet)

from magento-lts.

xsd-files-2024-05-02.zip

Added the files here from the webarchive links above, in case they disappear once more.

from magento-lts.

It seems microsoft fixed the problem.

I'm not sure the domain can be switched to a custom one, somebody could test this?

from magento-lts.

@alexh-swdev could you add a code review to #3980 pleaase?

from magento-lts.

<import namespace="http://schemas.xmlsoap.org/soap/encoding/" schemaLocation="http://schemas.xmlsoap.org/soap/encoding/" />

If we comment out or remove this line in all wsdl.xml and wsdl2.xml it seems to work.

Alternative is hosting the schema somewhere else and update schemaLocation to something else. i.e schemaLocation="http://somedomainthatmicrosoftdoesntbreak.xmlsoap.org/soap/encoding/"

from magento-lts.

Confirm, this URL returns 404.

from magento-lts.

I couldn't get it back to work by removing the statements from the wsdl.xml files. Pointing the URLs in the WSDL files to a self-hosted copy of the files also didn't help. Always got the error message "Couldn't find ...". As if the URL must always be schemas.xmlsoap.org or else it's invalid.

Now, I'm hosting http://schemas.xmlsoap.org/wsdl/soap/, http://schemas.xmlsoap.org/soap/encoding/ and http://schemas.xmlsoap.org/wdsl/ on my own server with exactly the same paths as before and aliased schemas.xmlsoap.org to my own server in the hosts file on all relevant systems (mostly ERM and CRM).

It's hacky, it's no long term solution, but it bought us some time until Microsoft get's their sh*t together (sorry) or until we can migrate over to a REST API.

from magento-lts.

Do we have a copy of these files? Can magento host these files instead?

from magento-lts.

Where can I find these files? Is there another site where I can download them?

from magento-lts.

There was a similar issue 2 years ago
#2223

from magento-lts.

Do we have a copy of these files?

I took them from the Internet Archive:
https://web.archive.org/web/20240228093904if_/https://schemas.xmlsoap.org/wsdl/soap/
https://web.archive.org/web/20240228093904if_/https://schemas.xmlsoap.org/soap/encoding/
https://web.archive.org/web/20240228093904if_/https://schemas.xmlsoap.org/wsdl/

Can magento host these files instead?

Not directly. To be able to replace schemas.xmlsoap.org with your own server, your server has to be respond to this domain name and it has to serve the files in this directory-like structrure as /wsdl/, /wsdl/soap/, /soap/encoding/. Magento can't build this url structure, so I modified the server config. With Caddy (https://caddyserver.com/) the rules would be:

http://schemas.xmlsoap.org {
    handle /wsdl/soap/ {
        rewrite * /var/www/foo/var/schemas/soap.xsd
        file_server
    }
    handle /soap/encoding/ {
        rewrite * /var/www/foo/var/schemas/encoding.xsd
        file_server
    }
    handle /wsdl/ {
        rewrite * /var/www/foo/var/schemas/wsdl.xsd
        file_server
    }
}

from magento-lts.

But magento could fix the .xml and .php files which reference that domain (http://schemas.xmlsoap.org) and replace them with a admin-controlles url instead. Then the files could be somewhere to your liking. Is that a bad idea?

from magento-lts.

https://schemas.xmlsoap.org server is up now

from magento-lts.

I also stumbled upon this.
I guess this already was an issue long time ago as this import was already comented out

So i commented it out in all xml files with no obvious issues.
Good to see it seems to be back online, but I think I'll keep it commented out.

/Edit: According to blame, since Magento CE 1.4.2.0

from magento-lts.

@Flyingmana @kiatng do you think it would be safe to remove the "import" of the schema as @alexh-swdev was showing in #3968 (comment)?

from magento-lts.

If it's safe to remove it, I prefer to avoid dependencies on external services.

Otherwise, could it be a valid and legitimate alternative if we host itself a copy of wsdl schema and changes all occurences?

like

• https://schemas.openmage.org/wsdl/
• https://schemas.openmage.org/wsdl/soap/
• https://schemas.openmage.org/soap/encoding/

then change in our copy version all references like this:

<!--
 
Copyright 2001 - 2005, International Business Machines Corporation and Microsoft Corporation
All Rights Reserved

License for WSDL Schema Files

...keep the copyright...
http://schemas.xmlsoap.org/wsdl/soap/2003-02-11.xsd
THESE SCHEMA FILES ARE PROVIDED "AS IS," AND THE AUTHORS MAKE NO REPRESENTATIONS 
...keep the copyright...
No other rights are granted by implication, estoppel or otherwise.
-->
<xs:schema targetNamespace="http://schemas.openmage.org/wsdl/soap/">
<xs:import namespace="http://schemas.openmage.org/wsdl/"/>
<xs:simpleType name="encodingStyle">
<xs:annotation>
<xs:documentation>
"encodingStyle" indicates any canonicalization conventions followed in the contents of the containing element. For example, the value "http://schemas.openmage.org/soap/encoding/" indicates the pattern described in SOAP specification
</xs:documentation>
</xs:annotation>
<xs:list itemType="xs:anyURI"/>
</xs:simpleType>

from the copyright i read also:

Original W3C files; http://www.w3.org/2001/06/soap-encoding
Changes made:
- reverted namespace to http://schemas.xmlsoap.org/soap/encoding/
- reverted root to only allow 0 and 1 as lexical values
- removed default value from root attribute declaration

from magento-lts.

If you host on openmage.org you are the bottleneck. Are you sure you want to do that?
If that file doesnt change, and is only there for some regulation, why not let the shop host the files? You are "talking" to the shop and they have to say how its done - not some external page?

That of course would mean some voodoo magic, since we'd have to have placeholders in these files and then switch them out somewhere early in the system (once).
Last time openmage changed some XML files.. didnt work quite well iirc.

from magento-lts.

(...). Last time openmage changed some XML files.. didnt work quite well iirc.

Well, it could have been better documented in the update, instead of hidden somewhere in the readme... But there's a sperate discussion about it afair ;)

Making those files part of OM would also be acceptable, I think, if removal would create issues. (But I would not host in on the OM servers). But if those really are not required... the less dependencies, the better :)

from magento-lts.

@pquerner

If that file doesnt change, and is only there for some regulation, why not let the shop host the files?

Do you mean to create routes that respond under the same domain as the shop? But in this case, all references inside the XML definitions should be dynamic, which becomes complicated.

from magento-lts.

Do you mean to create routes that respond under the same domain as the shop? But in this case, all references inside the XML definitions should be dynamic, which becomes complicated.

Yes, thats exactly how I mean it.
Or any other domain, which could be controlled by a system configuration.

from magento-lts.

if there's no need for it then let's remove it

from magento-lts.

can somebody test if SOAP APIs still work if we remove all the imports?

from magento-lts.

I removed the imports last week and I am using the api/v2_soap?wsdl=1 for product export with PHP clients and order import with PHP and c# clients and it looks still good...

from magento-lts.

thanks @alexh-swdev, I've created #3980

from magento-lts.

closed by #3980

from magento-lts.