So far,
in a whole new installation from scratch, from cvs head, I've got the very same bug. HTTP 302 then HTTP 200. Why does xml-rpc always answer with 302 at first?
Using a simple and functional xml-rpc remote call from lars-blogger
catch {xmlrpc::remote_call http://www.evex.co/RPC2 blogger.newPost -string "dsdsddfrerevgrtere" -int 1197 -string "mailto:iuri@iurix.com"; -string "GDGKGJEBSJjvijficFI$#44r45345" -string "text body" -boolean true} result
192.199.241.135 - - [09/Apr/2017:20:57:00 -0400] "POST /RPC2 HTTP/1.0" 302 299 "-" "NaviServer-Tcl/4.99"
192.199.241.135 - - [09/Apr/2017:20:57:00 -0400] "POST /RPC2/ HTTP/1.0" 200 122 "-" "NaviServer-Tcl/4.99"
179.34.179.254 - - [09/Apr/2017:20:57:05 -0400] "GET /test-ws HTTP/1.1" 502 575 "-" "Mozilla/5.0 (X11; Linux i686) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/40.0.2214.111 Safari/537.36"