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've just realised something by looking at Tracd logs. The following
note could shed some light on the above problem:
Note: Many pre-HTTP/1.1 user agents do not understand the 303
status. When interoperability with such clients is a concern, the
302 status code may be used instead, since most user agents react
to a 302 response as described here for 303.
So is it Tracd that's at fault here or is it the XML-RPC plugin which
doesn't know how to deal with 303?
The note appears here: http://www.w3.org/Protocols/rfc2616/rfc2616-
sec10.html
cheers,
-tomek
_______________________________________________
Trac mailing list
[email protected]
http://lists.edgewall.com/mailman/listinfo/trac
