On 20/07/2006, at 6:45 PM, Matthew Palmer wrote:
On Thu, Jul 20, 2006 at 05:47:54PM +1200, Tomek Piatek wrote:
I'm playing around with the XML-RPC plugin. I swear I had it going
the other
day and now I get this error:
xmlrpclib.ProtocolError: <ProtocolError for
dev:[EMAIL PROTECTED]/test/login/xmlrpc:
303 See Other>
I'm running latest development version of Trac and latest
reviosion of
XML-RPC. Trac is served with "tracd". All on a Debian box.
You too, huh? I've only just started playing with the XML-RPC
plugin, and
I've been getting 303 errors too (Ubuntu, python 2.4.1, trac as of
last
week). athomas hinted in my bug report (http://trac-hacks.org/
ticket/523,
but closed because I agree with him that throwing 303s is probably
more a
Trac problem than the plugin's) that other backends may be better,
so I'm
going to be working on that (specifically FastCGI) tomorrow. E-
mail me on
the weekend to ask how it went, because I'll probably forget to
update the
list otherwise.
I had a theory. I thought that it was because of how I actually get
to Trac. We're running LigHTTPd as our web server and we have a proxy
rule which sets up a proxy so that anything that goes to http://
trac.mydomain is relayed to localhost:9090 which is where tracd is
listening. So I tried this:
s = xmlrpclib.ServerProxy("html://login:[EMAIL PROTECTED]:9090/test/
login/xmlrpc")
s.system.listMethods()
No joy. Still get a 303. So it's not the proxying. My exact setup is:
Debian 3.1
Python 2.3.5
Trac r3530
XML-RPC r1047
One more thing. I've just tried adding "TRAC_ADMIN" permissions to
"anonymous" and then I issued the above command again but without the
"login" bin in the URL. It works fine. So it's something to do with
the authorisation system.
-t
_______________________________________________
Trac mailing list
[email protected]
http://lists.edgewall.com/mailman/listinfo/trac
