I'm currently working on a project where the WSDL is broken. The Java application that constructed the WSDL was unaware it was running behind a HTTPS proxy. This led to it importing HTTP URLs that didn't actually work.
The solution was to have Suds re-route specific URLs to resolve correctly. The fact that Suds is designed this way is testament to his common this problem is.
Yes, you can get HTTP servers that don't respect the safety of Get, but it's a much less common issue.
I run my Tomcat server with AXIS providing SOAP capabilities on localhost:8080 and front-end it with Apache using ProxyPass and ProxyPassReverse.
My SOAP web app runs fine, my Android test client also hits it with no complaints.
My Apache server can be hit with both HTTP and HTTPS which lets me use Apache to handle certificate management while I cna run any type of app server on localhost that I want.
So far no issues with this scenario. I used this for a contract I was just on and it also worked fine for both the SOAP and REST clients.
With SOAP, you know everything, just ask the server for its WSDL.