DO NOT REPLY [Bug 24869] - DigestScheme.authenticate returns invalid authorization string when algorithm is null

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24869. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.

Re: Problems with NTLM authentication

Roger, Just to make sure that there's no misunderstanding, Odi meant to say domain. Please make sure that you provide the correct domain host information to the NTCredentials constructor. Besides, 2.0rc2 was released with a pretty nasty bug that renders NTLM authentication completely

[PATCH] *Credentials constructors are sloppy

I think that UserNamePasswordCredentials should not allow null user name, as well as NTCredentials should not accept null NT domain and host. Especially NTCredentials in its present form can be too misleading. One may assume that feeding the constructor with null value instead of a real domain

DO NOT REPLY [Bug 24671] - Basic Authentification fails with non-ASCII username/password characters

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24671. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.

DO NOT REPLY [Bug 24671] - Basic Authentification fails with non-ASCII username/password characters

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24671. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.

DO NOT REPLY [Bug 24671] - Basic Authentification fails with non-ASCII username/password characters

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24671. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.

DO NOT REPLY [Bug 24671] - Basic Authentification fails with non-ASCII username/password characters

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24671. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.

Re: [PATCH] *Credentials constructors are sloppy

Looks good to me. Mike On Nov 22, 2003, at 1:00 PM, Oleg Kalnichevski wrote: I think that UserNamePasswordCredentials should not allow null user name, as well as NTCredentials should not accept null NT domain and host. Especially NTCredentials in its present form can be too misleading. One may

DO NOT REPLY [Bug 24671] - Basic Authentification fails with non-ASCII username/password characters

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24671. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.

DO NOT REPLY [Bug 24671] - Basic Authentification fails with non-ASCII username/password characters

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24671. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.

DO NOT REPLY [Bug 24671] - Basic Authentification fails with non-ASCII username/password characters

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24671. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.

Re: DO NOT REPLY [Bug 24671] - Basic Authentification fails with non-ASCII username/password characters

On Nov 22, 2003, at 6:31 PM, [EMAIL PROTECTED] wrote: --- Additional Comments From [EMAIL PROTECTED] 2003-11-22 23:31 --- The only question then would be if we want to allow another different charset for for the username/password before they are digested/base64 encoded. I think that