bogdan,
it is funny that abyss does not accept charset in request, but generates
one in its response. or perhaps it only accepts utf-8 or requires ""
around the value? according to rfc2616, "" are not needed, for example,
Media types are defined in section 3.7. An example of the field is
hmm...In our tests I saw no params for Content-type header. The
xmlrpc-c3 library used the abyss http server - will try do dig more
about this.
regards,
bogdan
Juha Heinanen wrote:
Juha Heinanen writes:
> Sent the following request:
>
> POST /RPC2 HTTP/1.0
> Host: 127.0.0.1
> Connectio
I just run some tests with a client built on the libxmlrpc-c3 (the same
used on the server side in openser). When sending a command without
params, the message looks like:
domain_dump
and works ok... so this is not the problem..sorry for misleading
you...your php library
On Friday 08 December 2006 14:00, Juha Heinanen wrote:
> i still have problem with empty params list. if there is no params, my
> php library produces an empty params list:
>
> POST /RPC2 HTTP/1.0
> Host: 127.0.0.1
> Connection: close
> User-Agent: OpenSIPg XML_RPC Client
> Content-Type: text/xml;
Juha Heinanen writes:
> Sent the following request:
>
> POST /RPC2 HTTP/1.0
> Host: 127.0.0.1
> Connection: close
> User-Agent: OpenSIPg XML_RPC Client
> Content-Type: text/xml; charset=ISO-8859-1
> Content-Length: 92
>
>
>
> domain_dump
>
i found the problem. openser xmlr
Bogdan-Andrei Iancu writes:
> if there is no parameters to the command, there is no need for the
> tag. So, you can try:
>
> POST /RPC2 HTTP/1.0
> Host: 127.0.0.1
> Connection: close
> User-Agent: OpenSIPg XML_RPC Client
> Content-Type: text/xml; charset=ISO-8859-1
> Content-Length: 15
Bogdan-Andrei Iancu writes:
> the "problem" is that the module uses the libxmlrpc-c3 library which
> provides functionality with a high level of encapsulation - will ask
> Lavinia if she can find a way to configure what is the URL required by
> server.
i still have problem with empty para
Hi Juha,
the "problem" is that the module uses the libxmlrpc-c3 library which
provides functionality with a high level of encapsulation - will ask
Lavinia if she can find a way to configure what is the URL required by
server.
as you probably noticed in README, there are more items on the todo
Bogdan-Andrei Iancu writes:
> the requested URL is not correct. Must be like:
>
> POST /RPC2 HTTP/1.0
i was able to produce this kind of header by giving "/RPC2" as location
parameter to the request. so it is not necessary to change the code
although i still think the code should not require
Bogdan-Andrei Iancu writes:
> the requested URL is not correct. Must be like:
>
> POST /RPC2 HTTP/1.0
bogdan,
i don't find that kind of requirement in xmlrpc spec:
Header requirements
The format of the URI in the first line of the header is not
specified. For example, it could be empty, a
Hi Juha,
the requested URL is not correct. Must be like:
POST /RPC2 HTTP/1.0
if there is no parameters to the command, there is no need for the
tag. So, you can try:
POST /RPC2 HTTP/1.0
Host: 127.0.0.1
Connection: close
User-Agent: OpenSIPg XML_RPC Client
Content-Type: text/xml; charset=IS
why 400 bad request?
-- juha
Sent the following request:
POST HTTP/1.0
Host: 127.0.0.1
Connection: close
User-Agent: OpenSIPg XML_RPC Client
Content-Type: text/xml; charset=ISO-8859-1
Content-Length: 155
lcr_dump
Hi Juha,
with the new MI interface there is no difference between the functions
accessible via fifo or xmlrpc, via sockunix or whatever - the function
name and its implementation is unique and it can be triggered via all
present transport mechanism (fifo & xmlrpc for the moment) - the name
a
i was going to try out Xmlrpc Module, but documentation is not very
clear.
- does each fifo command map to an xmlrpc function with the same name?
for example, if i want to execute lcr_reload fifo command, do i call
an xmprpc function with name "lcr_reload".
- if i want to execute a fifo com
14 matches
Mail list logo
