In the docs for Soap::Lite it states that the only change one needs to make to using HTTPS for Soap is to modify the ->proxy statement from 'http://' to 'https://'. Supposedly nothing needs to be changed on the server.
When I do this my client hangs at the call. Is there a problem with HTTPS when using Soap::transport::http::daemon as my server? Im sure Im missing some large step. Getting my data encrypted can't be *that* easy... can it?