14 Jul
2009
14 Jul
'09
11:42 a.m.
On 06-07 23:41, Juha Heinanen wrote:
i may be wrong, but it is hard for me to believe that
python xmlrpclib
would be badly broken, because it is very widely used.
I do not recall all the details, but I remember that I encountered the same
problem long time ago. I even reported it to the maintainer of the xmlrpc
library in python. He confirmed that this was a "shortcomming" in the library,
but refused to fix it because "all other xmlrpc servers close the connection".
In ser_ctl (the tools written in python) we patched the library, as far as I
can remember.
Jan.
if i look more closely at body of sr response:
##
T 2009/07/06 18:18:25.498713 192.98.101.10:6060 -> 192.98.101.10:37656 [AP]
HTTP/1.0 200 OK.
Via: SIP/2.0/TCP 192.98.101.10:37656.
Server: OpenXg SIP Router (2.99.0-dev01-serk (i386/linux)).
Content-Length: 108.
.
<?xml version="1.0"?>
<methodResponse>
<params>
<param>
<value></value>
</param>
</params>
</methodResponse>
#
i notice that each body line is terminated only by one char (cr or lf)
and the last line is not terminated by any char. content-length 108
seems to verify this.
i don't know if it is ok that lines end with only one char and that the
last line does not end with anything.
for comparison, mi xmlrpc module terminates each body line (including
the last) with both cr and lf:
#
T 2009/07/06 18:12:34.032315 192.98.101.10:6060 -> 192.98.101.10:41014 [AFP]
Content-length: 147.
Connection: close.
Date: Mon, 06 Jul 2009 16:12:34 GMT.
Server: XMLRPC_ABYSS/1.06.
.
<?xml version="1.0" encoding="UTF-8"?>.
<methodResponse>.
<params>.
<param><value><string></string></value></param>.
</params>.
</methodResponse>.
####
-- juha
_______________________________________________
sr-dev mailing list
sr-dev(a)lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev