https://bz.apache.org/bugzilla/show_bug.cgi?id=62312

--- Comment #2 from Joe Mokos <jmo...@riverbed.com> ---
I've uploaded a 2nd patch file generated from git that supersedes the 1st patch
file.  This patch file contains the following changes:

1.  The original algorithm used to choose the proxy authentication scheme
always chose the first Proxy-Authenticate header returned on the 407 response. 
Of course the first proxy I tried this on supported NTLM.  So "invalid
authentication scheme"  was logged and authorization failed.  I changed the
algorithm to choose the first Proxy-Authenticate header that contained a scheme
supported by the websocket client, ie Digest or Basic.

2.  The algorithm used to choose the WWW authenticate scheme had the same
problem as the proxy authenticate scheme so the same change was applied there.

3.  The variable arguments supplied to getString were not being appended to the
base message.  For instance, the exception messages for an unsupported auth
scheme rendered as "wsWebSocketContainer.unsupportedProxyAuthScheme" rather
than "wsWebSocketContainer.unsupportedProxyAuthScheme 407 NTLM".  {n} tokens
were added to first argument of getSTring to support the appropriate number of
variable arguments.

-- 
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

Reply via email to