greg.kujawa
2/2/2006 2:20:00 PM
Here is one thing I noticed looking into this deeper:
I can see things process okay on the Ruby xmlrpc/server, but it's where
the response is being passed back to the client where the problems
occur. I can successfully pass information back and forth with the Ruby
xmlrpc/server using other clients, such as Ruby, Python, and Smalltalk
xmlrpc clients. But just not with this SuperWaba xmlrpc client. I used
Ethereal to trace the TCP packets being passed and the successful
clients get a reply from the xmlrpc server, but the xmlrpc4sw clients
don't receive the response over the wire. The only difference I see in
the POST http header coming from the clients is that the SuperWaba
xmlrpc client is passing a Accept-Encoding: identity parameter, whereas
the other clients aren't. Could this be causing the problem since my
Ruby xmlrpc/server isn't using any encoding or authentication?
Is there any option for enabling this encoding/authentication on the
Ruby end to test it out?