10 Jun 23:17
Help debugging pingbacks
From: Toby Smithe <toby.smithe@...>
Subject: Help debugging pingbacks
Newsgroups: gmane.comp.web.pyblosxom.devel
Date: 2009-06-10 21:18:10 GMT
Subject: Help debugging pingbacks
Newsgroups: gmane.comp.web.pyblosxom.devel
Date: 2009-06-10 21:18:10 GMT
Hi,
I'm trying to fix up autopingback.py so that I can eventually think
about getting it into a plugin, and whilst I've now fixed it so that
it can send the request, when xmlrpclib receives the response object,
expat dies on trying to parse it. This is because, for some reason,
the stream (handled by xmlrpclib.Transport.request with the line
"h.getfile()") is not just HTTP. Instead, I get "33\n" twice, followed
by the config dict, then the expected information (Content-Type,
Content-Length and the xmlrpc response). The stream thus looks
something like
33
33
{ ....
... "config" : "stuff" ...
... }
Content-Type: text/xml
Content-Length: 226
<?xml version='1.0'?>
<methodResponse>
...
...
</methodResponse>
When I look in the "xmlrpc.py" plugin at the data at
xmlrpc.XMLRPCHandler._request.getResponse(), I only have the xml
returned in the stream. This suggests that somewhere between the
xmlrpc plug-in and autoping.py, the data is being mangled. It doesn't
(Continue reading)
RSS Feed