It's a customer of mine who is using Ruby. He sent a log that included the following user agent
I did a bit of research on soap4r. In the past there have been problems with soap faults, but they have been reported as fixed. So I thought maybe it is a formatting error in the response that is causing his client to receive the 500 error but ignore the soap fault in the content body.
As to the bug with SOAP::WSDL and the faultcode, I think I may have caused that myself...
die SOAP::WSDL::SOAP::Typelib::Fault11->new( { faultcode => 'soap:Server', faultstring => $msg } );
fyi, the log snippet I posted in my previous message was captured in soapUI when I was attempting to duplicate his issue.
(0)
]
