[issue7606] test_xmlrpc fails with non-ascii path

STINNER Victor added the comment: If anyone would like to work on non-ASCII HTTP header, please open a new issue with a pointer to this one. -- ___ Python tracker ___ __

[issue7606] test_xmlrpc fails with non-ascii path

STINNER Victor added the comment: > Commited: r80112 (py3k) Looks good: r80118 (3.1). -- resolution: -> fixed status: open -> closed ___ Python tracker ___

[issue7606] test_xmlrpc fails with non-ascii path

STINNER Victor added the comment: Commited: r80112 (py3k). Waiting for the buildbots before te backport to 3.1. -- ___ Python tracker ___

[issue7606] test_xmlrpc fails with non-ascii path

Antoine Pitrou added the comment: > What do you think about my solution (convert the traceback to ASCII to > avoid the encoding issue)? It's fine for me. Perhaps you should add a comment to explain why this is necessary. -- ___ Python tracker

[issue7606] test_xmlrpc fails with non-ascii path

STINNER Victor added the comment: What do you think about my solution (convert the traceback to ASCII to avoid the encoding issue)? If you would like to support non-ASCII characters in HTTP headers, you should open a new issue. For the compatibility, I prefer to use pure ASCII headers because

[issue7606] test_xmlrpc fails with non-ascii path

STINNER Victor added the comment: pitrou> If it's only about transmitting the string representation of the pitrou> traceback, perhaps we can simply use "replace" or "ignore" as the error pitrou> handler? Both replace and ignore loose information. My patch keeps all information by using backsla

[issue7606] test_xmlrpc fails with non-ascii path

STINNER Victor added the comment: #7608 was a duplicate issue. Copy of my message (msg98091): - SimpleXMLRPCRequestHandler.do_POST() writes the traceback in the HTTP header "X-traceback". But an HTTP header value is ASCII only, whereas a traceback can contain any character (eg. an non-ASCI

[issue7606] test_xmlrpc fails with non-ascii path

Martin v. Löwis added the comment: Antoine: sure, to fix the issue at hand, we can work-around. However, the issue of sending non-ASCII headers in HTTP remains, and should also be fixed. -- ___ Python tracker

[issue7606] test_xmlrpc fails with non-ascii path

Martin v. Löwis added the comment: David: I think it's a little bit more complicated. RFC 2616 says that the value of a header is *TEXT, which is defined as The TEXT rule is only used for descriptive field contents and values that are not intended to be interpreted by the message parser.

[issue7606] test_xmlrpc fails with non-ascii path

Antoine Pitrou added the comment: If it's only about transmitting the string representation of the traceback, perhaps we can simply use "replace" or "ignore" as the error handler? -- ___ Python tracker

[issue7606] test_xmlrpc fails with non-ascii path

R. David Murray added the comment: A little googling came up with this page: http://publib.boulder.ibm.com/infocenter/tivihelp/v2r1/topic/com.ibm.itame.doc/am61_webseal_admin570.htm Their solution is to uri encode the UTF8 encoded data. However, this article references the RFCs, which look li

[issue7606] test_xmlrpc fails with non-ascii path

Martin v. Löwis added the comment: > self.send_header("X-traceback", traceback.format_exc()) That's fairly tricky. send_header expects two strings (bytes are not acceptable), and also requires these strings to be ASCII. This is why it breaks: format_exc returns a non-ASCII string. I see tw

[issue7606] test_xmlrpc fails with non-ascii path

New submission from Antoine Pitrou : I configured my buildbot to use a non-ascii path to the interpreter and test_xmlrpc fails as follows: Exception happened during processing of request from ('127.0.0.1', 59091) Traceback (most recent call last): File