I seem to remember that an issue was fixed where the base64 encoding of the basic auth credentials was inserting line breaks at character number 76 in accordance with MIME specifications for base64. Of course that won't work in an HTTP header as you see in the error you are receiving. I can't find the specific issue right now, so I'm not sure which version it was fixed in (1.0.2 maybe?). Restlet version 1.0.5 works correctly though.
-----Original Message----- From: news [mailto:[EMAIL PROTECTED] On Behalf Of Philip Johnson Sent: Monday, September 24, 2007 3:51 PM To: [email protected] Subject: Basic Authentication name/password length restrictions Greetings, all, I am using Restlet with great pleasure to build a distributed set of web services using HTTP Basic authentication. I have run into the following occasional error from my Restlet-based client: 1002: Unable to send the HTTP request. Illegal character(s) in message header value: Basic VGVzdE11bHRpU2hlbGxVc2VyQGhhY2t5c3RhdC5vcmc6VGVzdE11bHRpU2hlbGxVc2VyQGhh Y2t5 c3RhdC5vcmc= After a fair amount of fiddling around, my hypothesis is that the problem has to do with the length of the username and/or password: they appear to need to be less than or equal to 26 characters in length. At least, the problem seems to go away when I reduce the string length to less than 26. I have done some googling and failed to discover such restrictions on HTTP Basic Authentication, so I am wondering if this possibly has something to do with Restlet. Could someone with more experience with Basic authentication enlighten me on whether this is a Restlet issue, a Basic authentication issue, or perhaps something else entirely? Thanks very much Philip Johnson
