Sorry, I was bit too fast with my answer. Especially about the configuration of the web service on the side of 4D. This was my from remembering of using a 4D web service for testing purposes in the past. At this time we built this test service as a mockup of another external web service, that should be used in production later. But as I said it was some time ago, so my assumption to configure a hardcoded endpoint in 4D was wrong.
I did a small test now, there wasn't any problem accessing the 4d web service via https. The mentioned endpoint is offered correctly by 4D. E.g. if you access an URL https://my.superwebservice/4dwsdl then this endpoint can be found within the wsdl. Accessing the wsdl using the 4d web services assistant works without any problem. This was tested with 4D v16 and V17. > -----Original Message----- > Lutz said: > "is not only necessary to access the endpoint with https:// you have to > offer the service > as a https:// service, e.g. you have to adjust the settings in 4D to modify > the wsdl in > the proper way." Regards Lutz -- Lutz Epperlein ---------------------------------------------- Agendo Gesellschaft für politische Planung mbH Köpenicker Str. 9 10997 Berlin http://www.agendo.de/ ---------------------------------------------- ********************************************************************** 4D Internet Users Group (4D iNUG) Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:4d_tech-unsubscr...@lists.4d.com **********************************************************************
