Skip to content

Ship the SOAP encoding schema instead of fetching it - #1501

Open
DylanMerigaud wants to merge 1 commit into
mvantellingen:mainfrom
DylanMerigaud:bundle-soap-encoding-schema
Open

DylanMerigaud wants to merge 1 commit into
mvantellingen:mainfrom
DylanMerigaud:bundle-soap-encoding-schema

Conversation

@DylanMerigaud

Copy link
Copy Markdown

Fixes #1417: zeep ships the W3C-licensed SOAP encoding schema and reads it locally, so a 404 or forbid_external can't block it. Apps packaged without zeep's package data fetch it as before. The four new tests fail on main and pass here. I left CHANGES to you.

This change was prepared with AI assistance (Claude).

zeep loads http://schemas.xmlsoap.org/soap/encoding/ whenever a WSDL
uses SOAP-ENC types, including through the automatic import of that
namespace. When the server is unreachable or answers 404 the WSDL fails
to load, and with forbid_external enabled the load is refused.

Ship a copy of the schema (the file already used by the tests, with its
W3C license notice unchanged) and load it from the package for the http
and https URLs instead of going through the transport. When the file is
missing, for example in an application packaged without zeep's package
data, the schema is loaded through the transport as before.

Fixes: mvantellingen#1417
Co-Authored-By: Claude Opus 5.5 <[email protected]>

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Getting 404 on loading https://schemas.xmlsoap.org/soap/encoding/

1 participant