net-dev  

Messages by Thread

• • Re: RFR: 8382582: Remove the experimental JVMCI feature [v6] Manuel Hässig
  • Re: RFR: 8382582: Remove the experimental JVMCI feature [v7] Manuel Hässig
  • Re: RFR: 8382582: Remove the experimental JVMCI feature [v7] Vladimir Kozlov
  • Re: RFR: 8382582: Remove the experimental JVMCI feature [v7] jonghoonpark
  • Re: RFR: 8382582: Remove the experimental JVMCI feature [v7] Manuel Hässig
  • Re: RFR: 8382582: Remove the experimental JVMCI feature [v7] Tobias Hartmann
  • Re: RFR: 8382582: Remove the experimental JVMCI feature [v8] Manuel Hässig
  • Re: RFR: 8382582: Remove the experimental JVMCI feature [v8] Tobias Hartmann
  • Re: RFR: 8382582: Remove the experimental JVMCI feature [v8] Vladimir Kozlov
  • Re: RFR: 8382582: Remove the experimental JVMCI feature [v8] Manuel Hässig
  • Integrated: 8382582: Remove the experimental JVMCI feature Manuel Hässig
• RFR: JDK-8382118: Refactor open/test/jdk/sun/net/www/protocol/file/DirPerm… Mahendra Chhipa
  • Re: RFR: JDK-8382118: Refactor open/test/jdk/sun/net/www/protocol/file/DirPerm… Marcono1234
  • Re: RFR: JDK-8382118: Refactor open/test/jdk/sun/net/www/protocol/file/DirPerm… Daniel Fuchs
  • Re: RFR: JDK-8382118: Refactor open/test/jdk/sun/net/www/protocol/file/DirPermissionDenied.java‎ test [v2] Mahendra Chhipa
  • Re: RFR: 8382118: Refactor open/test/jdk/sun/net/www/protocol/file/DirPermissionDenied.java test [v2] Daniel Fuchs
  • Integrated: 8382118: Refactor open/test/jdk/sun/net/www/protocol/file/DirPermissionDenied.java test Mahendra Chhipa
• RFR: 8382928: Add documentation to java.net.URI.normalize about empty segments Volkan Yazici
  • Re: RFR: 8382928: Add documentation to java.net.URI.normalize about empty segments Alan Bateman
  • Re: RFR: 8382928: Add documentation to java.net.URI.normalize about empty segments [v2] Volkan Yazici
  • Re: RFR: 8382928: Add documentation to java.net.URI.normalize about empty segments [v2] Volkan Yazici
  • Re: RFR: 8382928: Add documentation to java.net.URI.normalize about empty segments [v2] Daniel Fuchs
  • Re: RFR: 8382928: Add documentation to java.net.URI.normalize about empty segments [v2] Alan Bateman
  • Re: RFR: 8382928: Add documentation to java.net.URI.normalize about empty segments [v2] Volkan Yazici
  • Re: RFR: 8382928: Add documentation to java.net.URI.normalize about empty segments [v2] Volkan Yazici
  • Re: RFR: 8382928: Add documentation to java.net.URI.normalize about empty segments [v3] Volkan Yazici
  • Re: RFR: 8382928: Add documentation to java.net.URI.normalize about empty segments [v3] Daniel Fuchs
  • Re: RFR: 8382928: Add documentation to java.net.URI.normalize about empty segments [v3] Volkan Yazici
  • Re: RFR: 8382928: Add documentation to java.net.URI.normalize about empty segments [v4] Volkan Yazici
  • Re: RFR: 8382928: Add documentation to java.net.URI.normalize about empty segments [v4] Daniel Fuchs
  • Re: RFR: 8382928: Add documentation to java.net.URI.normalize about empty segments [v4] Alan Bateman
  • Integrated: 8382928: Add documentation to java.net.URI.normalize about empty segments Volkan Yazici
• RFR: 8384486: NTLM tests fail on Windows 11 and Windows Server 2025 Ashay Rane
  • Re: RFR: 8384486: NTLM tests fail on Windows 11 and Windows Server 2025 Jaikiran Pai
  • Re: RFR: 8384486: NTLM tests fail on Windows 11 and Windows Server 2025 Jaikiran Pai
  • Re: RFR: 8384486: NTLM tests fail on Windows 11 and Windows Server 2025 Daniel Fuchs
  • Re: RFR: 8384486: NTLM tests fail on Windows 11 and Windows Server 2025 [v2] Ashay Rane
  • Re: RFR: 8384486: NTLM tests fail on Windows 11 and Windows Server 2025 [v2] Jaikiran Pai
  • Re: RFR: 8384486: NTLM tests fail on Windows 11 and Windows Server 2025 [v2] Daniel Fuchs
  • Re: RFR: 8384486: NTLM tests fail on Windows 11 and Windows Server 2025 [v2] duke
  • Re: RFR: 8384486: NTLM tests fail on Windows 11 and Windows Server 2025 Ashay Rane
  • Re: RFR: 8384486: NTLM tests fail on Windows 11 and Windows Server 2025 Daniel Fuchs
  • Integrated: 8384486: NTLM tests fail on Windows 11 and Windows Server 2025 Ashay Rane
• RFR: 8377070: Update jimage format to support classes compiled with preview feature enabled Alan Bateman
  • Re: RFR: 8377070: Update jimage format to support classes compiled with preview feature enabled Jaikiran Pai
  • Re: RFR: 8377070: Update jimage format to support classes compiled with preview feature enabled Coleen Phillimore
  • Re: RFR: 8377070: Update jimage format to support classes compiled with preview feature enabled Severin Gehwolf
  • Re: RFR: 8377070: Update jimage format to support classes compiled with preview feature enabled Alan Bateman
  • Integrated: 8377070: Update jimage format to support classes compiled with preview feature enabled Alan Bateman
• Re: RFR: 8368695: Support 101 switching protocol in jdk.httpserver [v18] Josiah Noel
  • Re: RFR: 8368695: Support 101 switching protocol in jdk.httpserver [v18] Christoph Läubrich
  • Re: RFR: 8368695: Support 101 switching protocol in jdk.httpserver [v18] Josiah Noel
  • Re: RFR: 8368695: Support 101 switching protocol in jdk.httpserver [v18] Christoph Läubrich
• RFR: 8310138: Socket.isInputShutdown and isOutputShutdown don't specify what is returned when socket is closed Jaikiran Pai
  • Re: RFR: 8310138: Socket.isInputShutdown and isOutputShutdown don't specify what is returned when socket is closed Daniel Fuchs
  • Re: RFR: 8310138: Socket.isInputShutdown and isOutputShutdown don't specify what is returned when socket is closed [v2] Daniel Fuchs
  • Re: RFR: 8310138: Socket.isInputShutdown and isOutputShutdown don't specify what is returned when socket is closed Jaikiran Pai
  • Re: RFR: 8310138: Socket.isInputShutdown and isOutputShutdown don't specify what is returned when socket is closed Daniel Fuchs
  • Re: RFR: 8310138: Socket.isInputShutdown and isOutputShutdown don't specify what is returned when socket is closed Jaikiran Pai
  • Re: RFR: 8310138: Socket.isInputShutdown and isOutputShutdown don't specify what is returned when socket is closed [v2] Jaikiran Pai
  • Re: RFR: 8310138: Socket.isInputShutdown and isOutputShutdown don't specify what is returned when socket is closed [v2] Daniel Fuchs
  • Re: RFR: 8310138: Socket.isInputShutdown and isOutputShutdown don't specify what is returned when socket is closed [v2] Marcono1234
  • Re: RFR: 8310138: Socket.isInputShutdown and isOutputShutdown don't specify what is returned when socket is closed [v2] Daniel Fuchs
  • Re: RFR: 8310138: Socket.isInputShutdown and isOutputShutdown don't specify what is returned when socket is closed [v2] Jaikiran Pai
  • Re: RFR: 8310138: Socket.isInputShutdown and isOutputShutdown don't specify what is returned when socket is closed [v3] Jaikiran Pai
  • Re: RFR: 8310138: Socket.isInputShutdown and isOutputShutdown don't specify what is returned when socket is closed [v3] Jaikiran Pai
  • Re: RFR: 8310138: Socket.isInputShutdown and isOutputShutdown don't specify what is returned when socket is closed [v3] Daniel Fuchs
  • Re: RFR: 8310138: Socket.isInputShutdown and isOutputShutdown don't specify what is returned when socket is closed [v3] Michael McMahon
  • Re: RFR: 8310138: Socket.isInputShutdown and isOutputShutdown don't specify what is returned when socket is closed [v3] Jaikiran Pai
  • Re: RFR: 8310138: Socket.isInputShutdown and isOutputShutdown don't specify what is returned when socket is closed [v3] Alan Bateman
  • Re: RFR: 8310138: Socket.isInputShutdown and isOutputShutdown don't specify what is returned when socket is closed [v3] Jaikiran Pai
  • Re: RFR: 8310138: Socket.isInputShutdown and isOutputShutdown don't specify what is returned when socket is closed [v3] Alan Bateman
  • Re: RFR: 8310138: Socket.isInputShutdown and isOutputShutdown don't specify what is returned when socket is closed [v3] Daniel Fuchs
  • Re: RFR: 8310138: Socket.isInputShutdown and isOutputShutdown don't specify what is returned when socket is closed [v3] Jaikiran Pai
  • Re: RFR: 8310138: Socket.isInputShutdown and isOutputShutdown don't specify what is returned when socket is closed [v4] Jaikiran Pai
  • Re: RFR: 8310138: Socket.isInputShutdown and isOutputShutdown don't specify what is returned when socket is closed [v4] Jaikiran Pai
  • Re: RFR: 8310138: Socket.isInputShutdown and isOutputShutdown don't specify what is returned when socket is closed [v4] Jaikiran Pai
  • Re: RFR: 8310138: Socket.isInputShutdown and isOutputShutdown don't specify what is returned when socket is closed [v4] Alan Bateman
  • Re: RFR: 8310138: Socket.isInputShutdown and isOutputShutdown don't specify what is returned when socket is closed [v4] Alan Bateman
  • Re: RFR: 8310138: Socket.isInputShutdown and isOutputShutdown don't specify what is returned when socket is closed [v4] Jaikiran Pai
  • Re: RFR: 8310138: Socket.isInputShutdown and isOutputShutdown don't specify what is returned when socket is closed [v4] Alan Bateman
  • Re: RFR: 8310138: Socket.isInputShutdown and isOutputShutdown don't specify what is returned when socket is closed [v4] Jaikiran Pai
  • Re: RFR: 8310138: Socket.isInputShutdown and isOutputShutdown don't specify what is returned when socket is closed [v5] Jaikiran Pai
  • Re: RFR: 8310138: Socket.isInputShutdown and isOutputShutdown don't specify what is returned when socket is closed [v5] Daniel Fuchs
  • Re: RFR: 8310138: Socket.isInputShutdown and isOutputShutdown don't specify what is returned when socket is closed [v5] Jaikiran Pai
  • Integrated: 8310138: Socket.isInputShutdown and isOutputShutdown don't specify what is returned when socket is closed Jaikiran Pai
• Re: RFR: 8249824: s/n/w/p/https/HttpsURLConnection/CloseKeepAliveCached.java uses @ignore w/o bugid [v9] Mikhail Yankelevich
  • Re: RFR: 8249824: s/n/w/p/https/HttpsURLConnection/CloseKeepAliveCached.java uses @ignore w/o bugid [v9] Matthew Donovan
• Re: RFR: 8249824: s/n/w/p/https/HttpsURLConnection/CloseKeepAliveCached.java uses @ignore w/o bugid [v8] Mikhail Yankelevich
  • Re: RFR: 8249824: s/n/w/p/https/HttpsURLConnection/CloseKeepAliveCached.java uses @ignore w/o bugid [v8] Daniel Fuchs
  • Re: RFR: 8249824: s/n/w/p/https/HttpsURLConnection/CloseKeepAliveCached.java uses @ignore w/o bugid [v8] Mikhail Yankelevich
• RFR: 8381862: Refactor remaining TestNG tests under jdk/net/ExtendedSocketOption to use JUnit Daisuke Yamazaki
  • Re: RFR: 8381862: Refactor remaining TestNG tests under jdk/net/ExtendedSocketOption to use JUnit Alan Bateman
  • Re: RFR: 8381862: Refactor remaining TestNG tests under jdk/net/ExtendedSocketOption to use JUnit [v2] Daisuke Yamazaki
  • Re: RFR: 8381862: Refactor remaining TestNG tests under jdk/net/ExtendedSocketOption to use JUnit [v2] Daisuke Yamazaki
  • Re: RFR: 8381862: Refactor remaining TestNG tests under jdk/net/ExtendedSocketOption to use JUnit [v2] Daniel Fuchs
  • Re: RFR: 8381862: Refactor remaining TestNG tests under jdk/net/ExtendedSocketOption to use JUnit [v2] Daisuke Yamazaki
  • Re: RFR: 8381862: Refactor remaining TestNG tests under jdk/net/ExtendedSocketOption to use JUnit [v3] Daisuke Yamazaki
  • Re: RFR: 8381862: Refactor remaining TestNG tests under jdk/net/ExtendedSocketOption to use JUnit [v3] Marcono1234
  • Re: RFR: 8381862: Refactor remaining TestNG tests under jdk/net/ExtendedSocketOption to use JUnit [v3] Daisuke Yamazaki
  • Re: RFR: 8381862: Refactor remaining TestNG tests under jdk/net/ExtendedSocketOption to use JUnit [v4] Daisuke Yamazaki
  • Re: RFR: 8381862: Refactor remaining TestNG tests under jdk/net/ExtendedSocketOption to use JUnit [v4] Daniel Fuchs
  • Re: RFR: 8381862: Refactor remaining TestNG tests under jdk/net/ExtendedSocketOption to use JUnit [v4] Daisuke Yamazaki
  • Re: RFR: 8381862: Refactor remaining TestNG tests under jdk/net/ExtendedSocketOption to use JUnit [v4] duke
  • Integrated: 8381862: Refactor remaining TestNG tests under jdk/net/ExtendedSocketOption to use JUnit Daisuke Yamazaki
• RFR: 8381849: Refactor classes in /lib/testlibrary/bootlib to use JUnit instead of TestNG sstremler
  • Re: RFR: 8381849: Refactor classes in /lib/testlibrary/bootlib to use JUnit instead of TestNG sstremler
  • Re: RFR: 8381849: Refactor classes in /lib/testlibrary/bootlib to use JUnit instead of TestNG Andrey Turbanov
  • Re: RFR: 8381849: Refactor classes in /lib/testlibrary/bootlib to use JUnit instead of TestNG [v2] sstremler
  • Re: RFR: 8381849: Refactor classes in /lib/testlibrary/bootlib to use JUnit instead of TestNG [v2] Daniel Fuchs
  • Re: RFR: 8381849: Refactor classes in /lib/testlibrary/bootlib to use JUnit instead of TestNG [v2] Daniel Fuchs
  • Re: RFR: 8381849: Refactor classes in /lib/testlibrary/bootlib to use JUnit instead of TestNG [v2] sstremler
  • Re: RFR: 8381849: Refactor classes in /lib/testlibrary/bootlib to use JUnit instead of TestNG [v3] sstremler
  • Re: RFR: 8381849: Refactor classes in /lib/testlibrary/bootlib to use JUnit instead of TestNG [v3] Weijun Wang
  • Re: RFR: 8381849: Refactor classes in /lib/testlibrary/bootlib to use JUnit instead of TestNG [v3] Marcono1234
  • Re: RFR: 8381849: Refactor classes in /lib/testlibrary/bootlib to use JUnit instead of TestNG [v3] sstremler
  • Re: RFR: 8381849: Refactor classes in /lib/testlibrary/bootlib to use JUnit instead of TestNG [v4] sstremler
  • Re: RFR: 8381849: Refactor classes in /lib/testlibrary/bootlib to use JUnit instead of TestNG [v4] Marcono1234
  • Re: RFR: 8381849: Refactor classes in /lib/testlibrary/bootlib to use JUnit instead of TestNG [v4] SendaoYan
  • Re: RFR: 8381849: Refactor classes in /lib/testlibrary/bootlib to use JUnit instead of TestNG [v4] sstremler
  • Re: RFR: 8381849: Refactor classes in /lib/testlibrary/bootlib to use JUnit instead of TestNG [v5] sstremler
• RFR: 8331996: JFR: Add boolean check before loading event classes Robert Toyonaga
  • Re: RFR: 8331996: JFR: Add boolean check before loading event classes Alan Bateman
  • Re: RFR: 8331996: JFR: Add boolean check before loading event classes ExE Boss
  • Re: RFR: 8331996: JFR: Add boolean check before loading event classes [v2] Robert Toyonaga
  • Re: RFR: 8331996: JFR: Add boolean check before loading event classes [v2] Robert Toyonaga
  • Re: RFR: 8331996: JFR: Add boolean check before loading event classes [v2] Robert Toyonaga
  • Re: RFR: 8331996: JFR: Add boolean check before loading event classes [v2] Alan Bateman
  • Re: RFR: 8331996: JFR: Add boolean check before loading event classes [v2] Robert Toyonaga
  • Re: RFR: 8331996: JFR: Add boolean check before loading event classes [v3] Robert Toyonaga
  • Re: RFR: 8331996: JFR: Add boolean check before loading event classes [v3] Alan Bateman
  • Re: RFR: 8331996: JFR: Add boolean check before loading event classes [v3] Thomas Stuefe
  • Re: RFR: 8331996: JFR: Add boolean check before loading event classes [v3] Robert Toyonaga
• Re: RFR: 8249824: s/n/w/p/https/HttpsURLConnection/CloseKeepAliveCached.java uses @ignore w/o bugid [v7] Mikhail Yankelevich
  • Re: RFR: 8249824: s/n/w/p/https/HttpsURLConnection/CloseKeepAliveCached.java uses @ignore w/o bugid [v7] Daniel Fuchs
  • Re: RFR: 8249824: s/n/w/p/https/HttpsURLConnection/CloseKeepAliveCached.java uses @ignore w/o bugid [v7] Mikhail Yankelevich
• RFR: 8308878: com/sun/net/httpserver/simpleserver/OutputFilterTest.java fails with assertion errors in IPv6 only environment Jaikiran Pai
  • Re: RFR: 8308878: com/sun/net/httpserver/simpleserver/OutputFilterTest.java fails with assertion errors in IPv6 only environment Daniel Fuchs
  • Re: RFR: 8308878: com/sun/net/httpserver/simpleserver/OutputFilterTest.java fails with assertion errors in IPv6 only environment Marcono1234
  • Re: RFR: 8308878: com/sun/net/httpserver/simpleserver/OutputFilterTest.java fails with assertion errors in IPv6 only environment [v2] Jaikiran Pai
  • Re: RFR: 8308878: com/sun/net/httpserver/simpleserver/OutputFilterTest.java fails with assertion errors in IPv6 only environment [v2] Jaikiran Pai
  • Re: RFR: 8308878: com/sun/net/httpserver/simpleserver/OutputFilterTest.java fails with assertion errors in IPv6 only environment [v2] Jaikiran Pai
  • Re: RFR: 8308878: com/sun/net/httpserver/simpleserver/OutputFilterTest.java fails with assertion errors in IPv6 only environment [v2] Daniel Fuchs
  • Re: RFR: 8308878: com/sun/net/httpserver/simpleserver/OutputFilterTest.java fails with assertion errors in IPv6 only environment [v2] Jaikiran Pai
  • Integrated: 8308878: com/sun/net/httpserver/simpleserver/OutputFilterTest.java fails with assertion errors in IPv6 only environment Jaikiran Pai
• RFR: 8383248: Reduce buffer allocations for HTTP headers instead of allocating 16KB per request Ashay Rane
  • Re: RFR: 8383248: Reduce buffer allocations for HTTP headers instead of allocating 16KB per request [v2] Ashay Rane
  • Re: RFR: 8383248: Reduce buffer allocations for HTTP headers instead of allocating 16KB per request [v2] Ashay Rane
  • Re: RFR: 8383248: Reduce buffer allocations for HTTP headers instead of allocating 16KB per request [v2] Jaikiran Pai
  • Re: RFR: 8383248: Reduce buffer allocations for HTTP headers instead of allocating 16KB per request [v2] Jaikiran Pai
  • Re: RFR: 8383248: Reduce buffer allocations for HTTP headers instead of allocating 16KB per request [v2] Jaikiran Pai
  • Re: RFR: 8383248: Reduce buffer allocations for HTTP headers instead of allocating 16KB per request [v2] Jaikiran Pai
  • Re: RFR: 8383248: Reduce buffer allocations for HTTP headers instead of allocating 16KB per request [v2] Daniel Fuchs
  • Re: RFR: 8383248: Reduce buffer allocations for HTTP headers instead of allocating 16KB per request [v2] Jaikiran Pai
  • Re: RFR: 8383248: Reduce buffer allocations for HTTP headers instead of allocating 16KB per request [v2] Ashay Rane
  • Re: RFR: 8383248: Reduce buffer allocations for HTTP headers instead of allocating 16KB per request Ashay Rane
  • Re: RFR: 8383248: Reduce buffer allocations for HTTP headers instead of allocating 16KB per request [v3] Ashay Rane
  • Re: RFR: 8383248: Reduce buffer allocations for HTTP headers instead of allocating 16KB per request [v3] Jaikiran Pai
  • Re: RFR: 8383248: Reduce buffer allocations for HTTP headers instead of allocating 16KB per request [v3] Ashay Rane
  • Re: RFR: 8383248: Reduce buffer allocations for HTTP headers instead of allocating 16KB per request [v3] Ashay Rane
  • Re: RFR: 8383248: Reduce buffer allocations for HTTP headers instead of allocating 16KB per request [v3] Jaikiran Pai
  • Re: RFR: 8383248: Reduce buffer allocations for HTTP headers instead of allocating 16KB per request [v3] Daniel Fuchs
  • Re: RFR: 8383248: Reduce buffer allocations for HTTP headers instead of allocating 16KB per request [v3] Daniel Fuchs
  • Re: RFR: 8383248: Reduce buffer allocations for HTTP headers instead of allocating 16KB per request [v4] Ashay Rane
  • Re: RFR: 8383248: Reduce buffer allocations for HTTP headers instead of allocating 16KB per request [v4] Jaikiran Pai
  • Re: RFR: 8383248: Reduce buffer allocations for HTTP headers instead of allocating 16KB per request [v4] Ashay Rane
  • Re: RFR: 8383248: Reduce buffer allocations for HTTP headers instead of allocating 16KB per request [v4] Jaikiran Pai
  • Re: RFR: 8383248: Reduce buffer allocations for HTTP headers instead of allocating 16KB per request [v4] Jaikiran Pai
  • Re: RFR: 8383248: Reduce buffer allocations for HTTP headers instead of allocating 16KB per request [v4] Jaikiran Pai
  • Re: RFR: 8383248: Reduce buffer allocations for HTTP headers instead of allocating 16KB per request [v4] Daniel Fuchs
  • Re: RFR: 8383248: Reduce buffer allocations for HTTP headers instead of allocating 16KB per request [v5] Ashay Rane
  • Re: RFR: 8383248: Reduce buffer allocations for HTTP headers instead of allocating 16KB per request [v5] Ashay Rane
  • Re: RFR: 8383248: Reduce buffer allocations for HTTP headers instead of allocating 16KB per request [v5] Jaikiran Pai
  • Re: RFR: 8383248: Reduce buffer allocations for HTTP headers instead of allocating 16KB per request [v5] Jaikiran Pai
  • Re: RFR: 8383248: Reduce buffer allocations for HTTP headers instead of allocating 16KB per request [v6] Ashay Rane
  • Re: RFR: 8383248: Reduce buffer allocations for HTTP headers instead of allocating 16KB per request [v6] Jaikiran Pai
  • Re: RFR: 8383248: Reduce buffer allocations for HTTP headers instead of allocating 16KB per request [v6] Jaikiran Pai
  • Re: RFR: 8383248: Reduce buffer allocations for HTTP headers instead of allocating 16KB per request [v6] Daniel Fuchs
  • Re: RFR: 8383248: Reduce buffer allocations for HTTP headers instead of allocating 16KB per request [v6] duke
  • Integrated: 8383248: Reduce buffer allocations for HTTP headers instead of allocating 16KB per request Ashay Rane
• RFR: 8383174: Improve exceptions in Java_sun_net_www_protocol_http_ntlm_NTLMAuthSequence_getNextToken Matthias Baesken
  • Re: RFR: 8383174: Improve exceptions in Java_sun_net_www_protocol_http_ntlm_NTLMAuthSequence_getNextToken Daniel Jeliński
  • Re: RFR: 8383174: Improve exceptions in Java_sun_net_www_protocol_http_ntlm_NTLMAuthSequence_getNextToken Christoph Langer
  • Re: RFR: 8383174: Improve exceptions in Java_sun_net_www_protocol_http_ntlm_NTLMAuthSequence_getNextToken Matthias Baesken
  • Integrated: 8383174: Improve exceptions in Java_sun_net_www_protocol_http_ntlm_NTLMAuthSequence_getNextToken Matthias Baesken
• RFR: Merge 99c2cd01c3f82b37ef7faac38a1b92a083c1ab91 Jaikiran Pai
  • Re: RFR: Merge 99c2cd01c3f82b37ef7faac38a1b92a083c1ab91 Daniel Fuchs
  • Re: RFR: Merge 99c2cd01c3f82b37ef7faac38a1b92a083c1ab91 [v2] Jaikiran Pai
  • Re: RFR: Merge 99c2cd01c3f82b37ef7faac38a1b92a083c1ab91 Jaikiran Pai
  • Integrated: Merge 99c2cd01c3f82b37ef7faac38a1b92a083c1ab91 Jaikiran Pai
• RFR: 8180483: sun.net.www.protocol.http.HttpClient::available may consume one character Volkan Yazici
  • Re: RFR: 8180483: sun.net.www.protocol.http.HttpClient::available may consume one character Volkan Yazici
  • Re: RFR: 8180483: sun.net.www.protocol.http.HttpClient::available may consume one character [v2] Volkan Yazici
  • Re: RFR: 8180483: sun.net.www.protocol.http.HttpClient::available may consume one character [v2] Volkan Yazici
  • Re: RFR: 8180483: sun.net.www.protocol.http.HttpClient::available may consume one character [v3] Volkan Yazici
  • Re: RFR: 8180483: sun.net.www.protocol.http.HttpClient::available may consume one character [v4] Volkan Yazici
  • Re: RFR: 8180483: sun.net.www.protocol.http.HttpClient::available may consume one character [v5] Volkan Yazici
  • Re: RFR: 8180483: sun.net.www.protocol.http.HttpClient::available may consume one character [v5] Daniel Fuchs
  • Re: RFR: 8180483: sun.net.www.protocol.http.HttpClient::available may consume one character [v5] Volkan Yazici
  • Integrated: 8180483: sun.net.www.protocol.http.HttpClient::available may consume one character Volkan Yazici

• Earlier messages
• Later messages