SOAP::Lite X.509 certificates, mod

habit_forming has asked for the wisdom of the Perl Monks concerning the following question:

Heeelllo Monks! Thy knowledge is a warm shelter to those caught on the desolate unforgiving arctic planes of confusion.

My problem is this. I have a SOAP::Lite service running on Apache 1.3.23 using mod_ssl; and that works great. No problems very fast, thank you very much.

The great thing about SOAP::Lite is that when a server side PM die's the die is transmitted back across the to the client side where a die is thrown and the proper things happen.

Well all is find and good until I try to use X.509 certificates. When I use certificates any die in the server side module causes the client to receive sslv3 read errors. The die message disappears and no useful information is sent back. However, if I just use a user name and password then die's work just fine.

Has anyone else seen this? If so, how did you deal with it? I really would like to able to get my die messages back.

--habit

Comment on SOAP::Lite X.509 certificates, mod_ssl and die Select or Download Code

Replies are listed 'Best First'.
Re: SOAP::Lite X.509 certificates, mod_ssl and die by tilly (Archbishop) on Aug 23, 2004 at 16:12 UTC
Have you looked for where error logs are kept on the server? Odds are extremely good that, regardless of what happens on the client side, your die message will be there.	[reply]
Re^2: SOAP::Lite X.509 certificates, mod_ssl and die by habit_forming (Monk) on Aug 23, 2004 at 16:38 UTC
Yes that is true but in the effort to make the function calls as transparent as possible it would be really nice if `die`'s actually worked the way they are suppose to. As a side I actually modified SOAP::Server such that `warn`'s would work properly as well. All in the effort to improve transparency. --habit	[reply] [d/l] [select]