[Zope3-dev] XMLRPC broken?

[Andreas Jung]

I fixed this on the trunk.

-aj

--On 23. Oktober 2005 14:08:24 +0200 Andreas Jung <lists at andreas-jung.com> 
wrote:

>
>
> --On 22. Oktober 2005 16:24:31 +0200 Adam Groszer <adamg at fw.hu> wrote:
>
>> I'm wondering if the XMLRPC server is broken on the trunk or just I'm
>> missing something?
>>
>> My app was surely working before the twisted integration. Since then I
>> had a HDD crash and tried it now with a fresh checkout.
>>
>> the request and response captured with TCPwatch looks like this:
>>
>> [00:00.000 - client 127.0.0.1:1689 forwarded to 127.0.0.1:8080]
>> POST /ap1/ HTTP/1.0
>> Host: localhost:8081
>> User-Agent: xmlrpclib.py/1.0.1 (by www.pythonware.com)
>> Content-Type: text/xml;charset=utf-8
>
> The choice of the publisher is tied to the content-type and the request
> method. Likely the chooseClasses() method takes "text/xml; charset=utf-8"
> as content-type to lookup a publisher but the xmlrpc publisher is
> registered as text/xml. So chooseClasses should ignore the 'charset...'
> part. Please file a collector issue and assign it to me (ajung).
>
> -aj
>
>



-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 186 bytes
Desc: not available
Url : http://mail.zope.org/pipermail/zope3-dev/attachments/20051023/ffce4377/attachment.bin