XML-RPC server is not protocol compliant

[mpalmer@…]

I think this log entry says it all:

localhost - - [19/Jul/2006 16:02:41] "POST /trac/login/xmlrpc HTTP/1.0" 303 -

Perhaps with a note that, AFAICT, HTTP/1.0 does not know about the 303 See Other response code.

[Alec Thomas]

This is an artifact of the way Trac authentication works, so there's not that much that can be done.

[Alec Thomas]

In fact, this is really an issue with Trac itself and should be raised on the main Trac site.

[anonymous]

Hmm, OK. I'll report the issue on the main Trac site. I've never noticed Trac proper throw a 303 (it's usually 302) when I log in via a web browser, though. Also, if I login and I get redirected, where do I actually send the real XMLRPC request to? I'm having trouble with requests just plain-up dying instead of completing properly ("Connection reset by peer", for example), and I noticed this problem as a side-effect of my attempts to debug the main problem. Basically, any authenticated XMLRPC request dies. Utterly heartbreaking.

[Alec Thomas]

I think I've encountered this before. Some of the Trac backends have issues, and some work :(

I'd suggest documenting all this in the ticket you raise.

[mpalmer@…]

I'm not adverse to switching backends if it'll solve the problem. I'm using tracd at the moment; do you have any recommendations for which one works Real Nice?

[John Hampton]

FYI, this did end up being a bug in trac, specifically ​LoginModule. cmlenz fixed it in ​changeset:3581 3581