UndefinedInterfaceName exception when used with gSoap 2.7 client

Bug #1188233 reported by André
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ladon
New
Undecided
Unassigned

Bug Description

I'm using Ladon 0.8.1 to expose SOAP services to a C/C++ client written on top of gSOAP 2.8.4 (Ubuntu 12.04 package).
When I tried to connect to my service the ladon-ctl testserver raised a UndefinedInterfaceName exception.

Using Wireshark I could see the client request and ladon-ctl stacktrace, see wireshark_soap.raw attached.
I'm not sure if it's the client that does malformed POST request or the server that doesn't handle it correctly, but I made a patch (ladon_parse_path_info.patch attached) for ladon/server/wsgi_application.py that solves the issue for me.
I've also attached a simple project (code.tar.gz) containing the Calculator web service and the gSOAP client source and Makefile for reproducing the issue.

Revision history for this message
André (andre-miras) wrote :
Revision history for this message
André (andre-miras) wrote :

Wireshark session attached.

Revision history for this message
André (andre-miras) wrote :

Project reproducing the issue attached.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.