Re: [9] RFR 8138953: HttpURLConnection doesn't fallback to another auth scheme if negotiate process failed

2015-10-15 Thread Artem Smotrakov
Hi Max, RFC 2617 [1] requires a user agent to use one of the challenges with the strongest auth scheme it understands (please see section 1.2): ... The user agent MUST choose to use one of the challenges with the strongest auth-scheme it understands and request credentials from the us

Re: WebSocket client API

2015-10-15 Thread Peter Levart
Hi Pavel, There's a RFR being discussed on core-libs-dev: "8138696 : java.lang.ref.Cleaner - an easy to use alternative to finalization". Although it does not currently support it, I have been doing experiments with FinalReference(s) (a package-private subtype of Reference that is used intern

Re: [9] RFR 8138953: HttpURLConnection doesn't fallback to another auth scheme if negotiate process failed

2015-10-15 Thread Wang Weijun
Let's go back to the bug description: But no fallback happens if: 1. an HTTP server supports both Negotiate (via Kerberos) and Basic authentication schemes 2. first, a user provides correct Kerberos credentials, and a connection is successfully established with Negotiate scheme 3. then, a us