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
> Connection: close
> User-Agent: OpenSIPg XML_RPC Client
> Content-Type: text/xml; charset=ISO-8859-1
> Content-Length: 92
>
> <?xml version="1.0" ?>
> <methodCall>
> <methodName>domain_dump</methodName>
> </methodCall>
i found the problem. openser xmlrpc server does not like
charset=ISO-8859-1 in Content-type. the problem is that some other
servers require it if xml document contains non-ascii chars such as รค.
the spec says:
The Content-Type is text/xml.
but does not mention if any additional specifiers are allowed or not.
as i said, i have used this library for many years against many servers
and this is the first time when charset=ISO-8859-1 gives problems.
i guess i need to hack my xmlrpc call by giving it an extra parameters
that tells if charset is added or not.
-- juha
_______________________________________________
Devel mailing list
[email protected]
http://openser.org/cgi-bin/mailman/listinfo/devel
