[ejabberd] xmlrpc compiled?

Liam ejabberd at networkimprov.net
Sat Jan 9 01:49:31 MSK 2010


Thanks for the config and HTTP traffic details...

Having mirrored those, I'm still getting HTTP result 415. The ejabberd log
is telling me:

=ERROR REPORT==== 2010-01-08 14:44:51 ===
{tcp_serv,139,{xmlrpc_http,handler,timeout}}

Which sorta implies the xmlrpc module isn't reaching ejabberd_xmlrpc?


On Thu, Jan 7, 2010 at 10:16 PM, Liam <ejabberd at networkimprov.net> wrote:

> On deeper inspection, I gather an authentication struct comes before a
> command struct, so my xmlrpc msg is:
>
>
> <methodcall>
> <methodname>register</methodname>
> <params><param><value><struct>
>
> <member><name>user</name><value><string>xmlrpc_access</string></value></member>
>
> <member><name>server</name><value><string>localhost</string></value></member>
> <member><name>password</name><value><string>pass</string></value></member>
> </struct></value></param><param><value><struct>
> <member><name>user</name><value><string>newuser</string></value></member>
> <member><name>host</name><value><string>localhost</string></value></member>
>
> <member><name>password</name><value><string>newpass</string></value></member>
>
> </struct></value></param></params></methodcall>
>
> However, I'm getting back an empty response with HTTP result 415 (invalid
> media). The headers:
>
> Server: nginx/0.7.62
> Date: Fri, 08 Jan 2010 05:59:38 GMT
> Content-Type: text/xml
> Connection: keep-alive
> Content-Length: 0
>
> (I proxy the request via nginx; I'm sure it's handing it on.)
>
> Ideas?
>
>
>
> On Thu, Jan 7, 2010 at 2:47 PM, Liam <ejabberd at networkimprov.net> wrote:
>
>> >Also note that the Guide says [1]:
>> > If at least one restriction is defined, then the frontend expects that
>> > authentication information is provided when executing a command.
>> >
>> >That means you will have to provide auth of some Jabber account inside
>> the XMLRPC calls.
>>
>> I don't see from the xmlrpc readme how to include authentication in an
>> xmlrpc call.
>>
>> My xmlrpc text looks like:
>>
>> <methodcall>
>>   <methodname>register</methodname>
>>   <params><param><value><struct>
>>
>> <member><name>user</name><value><string>username</string></value></member>
>>
>> <member><name>host</name><value><string>hostname</string></value></member>
>>
>> <member><name>password</name><value><string>password</string></value></member>
>> </struct></value></param></params></methodcall>
>>
>>
>>
>> On Mon, Jan 4, 2010 at 11:30 AM, Liam <ejabberd at networkimprov.net> wrote:
>>
>>> It's disappointing that the xmlrpc components aren't distributed in a
>>> single, compiled package...
>>>
>>> Having installed the compiled erlang xmlrpc module, I see ejabberd_xmlrpc
>>> isn't distributed as a .beam... Any pointers to one? Or can I compile from
>>> WinXP command line?
>>>
>>> There's a bin (but no ebin) directory in my WinXP ejabberd directory...
>>> Same as ebin?
>>>
>>> I want ANY XMLRPC client to be able to use ONLY the register command...
>>> Is this the config for that:
>>>
>>>   {4560, ejabberd_xmlrpc, [{access_commands, [{all, [register], []}]}]},
>>>
>>>
>>> Liam
>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.jabber.ru/pipermail/ejabberd/attachments/20100108/7546b6e6/attachment.html>


More information about the ejabberd mailing list