Bug #229

Whitespace problem with XMLRPC API

Added by victor-typotrac-carotena-net - 1329 days ago. Updated 790 days ago.

Status :Closed Start :
Priority :Normal Due date :
Assigned to :scoop - % Done :

0%
Category :backend
Target version :release2
Resolution :

wontfix

Description

I've been trying to use typo (the SVN version) with the windows versions of ecto. This client sends \r\n newlines in between the elements of the XML request. This seems to choke typo.
Perhaps it is ActionWebService, I'm not sure.
In any case, this format of XML shouldn't give problems.

This was found on the development log:

Processing BackendController#xmlrpc (for 195.224.245.170 at Tue Apr 12 12:46:21 GMT 2005)
  Parameters: {"<?xml version"=>"\"1.0\"?>\r\n<methodCall>\r\n  <methodName>blogger.getUsersBlogs</methodName>\r\n  <params>\r\n    <param>\r\n      <value>\r\n        <string />\r\n      </value>\r\n    </param>\r\n    <param>\r\n      <value>\r\n        <string>victor</string>\r\n      </value>\r\n    </param>\r\n    <param>\r\n      <value>\r\n        <string>whatever</string>\r\n      </value>\r\n    </param>\r\n  </params>\r\n</methodCall>", "action"=>"xmlrpc", "controller"=>"backend", "backend/xmlrpc"=>nil}
Completed in 0.088640 (11 reqs/sec)

It also could be the empty appkey, but since the API spec says it is not significant, I guess that won't be the case.

Associated revisions

Revision bca9645e96778b90c9d762df80aa651584f962b7
Added by scoop 1223 days ago

Fixed label for attributes on article creation form (closes #229) []

git-svn-id: http://svn.typosphere.org/typo/trunk@460 820eb932-12ee-0310-9ca8-eeb645f39767

History

04/12/2005 01:49 PM - scoop -

Could you be a little more specific about the "choking" part? What exactly does go wrong? Did you find anything else in development.log besides the request itself?

04/15/2005 09:17 AM - Redmine Admin

The server reports an error 500 with the following text: Malformed SOAP or XML-RPC protocol message.

Nothing else is found on the log.

I've also noticed similar behaviour from SharpMT, when the client formats the body of the article to contain newlines in \r\n form

04/18/2005 01:06 PM - scoop -

In an attempt to duplicate this I managed to successfully work with my blog using w.bloggar. Ecto for Windows failed miserably spitting random error messages at me before even getting to the point where it'd talk to to XML-RPC backend and SharpMT 2 tried to issue getCategoriesForPost from the MT API via the metaWeblogAPI (which obviously isn't in the spec and thus not supposed to work). I'll keep trying (and love MarsEdit in the meantime ;) )

04/23/2005 09:22 PM - scoop -

  • Status changed from New to Closed
  • Resolution set to wontfix

I'll resolve this for now. There's nothing much we can do here since the error (if any, the blog editors don't really behave correctly, see above) is most likely based around AWS and not typo.

Also available in: Atom PDF