bad response from server, 200 [parsererror, list]

[GoogleCodeExporter]

I am able to bring up the interface in Firefox, but
nothing works; I only get error messages like these:

Bad response from server: (200 [parsererror,list]) 
Bad response from server: (200 [parsererror,getsettings]) 

I guess this "200" is http error code, which in that case
actually means "OK". So is there just some kind of parsing
error?

I'm running rtorrent on server A, and Apache (I think
2.2.3 on CentOS 5.4) on B. I have set scgi_port=:5577,
and it is reachable from from B. (xmlrpc-c is 1.21.2).
Should it be possible to use xmlrpc(1) on this port?
I thought that it really shouldn't, but I am a bit
confused on the matter.

(I do get error from that. But then, rtorrent
is not a web server, it shouldn't do HTTP POST!?

xmlrpc localhost:5577 system.client_version
Error: libcurl failed to execute the HTTP POST transaction.
Empty reply from server (-504))

Further, I cannot add mod_scgi at the moment, so I
popped in the rpc plugin.

I have a feeling I am doing something wrong, but I have
also tried every possibility according to my current
knowledge. For example, if I remove the rpc-plugin I
directly get some other error, which means something
IS going through there. The same if I stop rtorrent.
And the webui does display the version number of
rtorrent, "0.8.6/0.12.6".

Everything seems ok, but it just doesn't work...

Original issue reported on code.google.com by daniel.l...@gmail.com on 23 Mar 2010 at 9:23

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

i missread your issue at first

Original comment by Wonslung@gmail.com on 23 Mar 2010 at 10:36

• Changed state: New

[GoogleCodeExporter]

you need to make sure you're scgi is set up to ALLOW the remote source...I 
forget how 
to do this but will try to look into it

i am pretty sure for this type of config you will NEED to use an external scgi 
system.

the rpc plugin isn't going to work.

Original comment by Wonslung@gmail.com on 23 Mar 2010 at 10:38

[GoogleCodeExporter]

The problem was that I had symlinked the rpc plugin to the plugins-directory. I 
was
well within bounds for the webserver, but that one just didn't care to follow
symlinks I suppose...

Otherwise everything works as I thought, and my setup is perfectly fine.

Original comment by daniel.l...@gmail.com on 24 Mar 2010 at 12:20

[GoogleCodeExporter]

so it's working now?

Original comment by Wonslung@gmail.com on 24 Mar 2010 at 1:19

[GoogleCodeExporter]

also, if you're using apache, and the sym link points to a dir which doesn't 
have 
permissions, you'll have problems

Original comment by Wonslung@gmail.com on 24 Mar 2010 at 1:57

[GoogleCodeExporter]

Yes, it works. Invalid bug...

Original comment by daniel.l...@gmail.com on 24 Mar 2010 at 10:52

[GoogleCodeExporter]

Original comment by novik65 on 24 Mar 2010 at 11:39

• Changed state: Invalid