net-dev  

Messages by Thread

• • Integrated: 8357406: Remove usages of jdk.tracePinnedThreads system property from httpclient tests Jaikiran Pai
  • Re: RFR: 8357406: Remove usages of jdk.tracePinnedThreads system property from httpclient tests Jaikiran Pai
• RFR: 8304065: HttpServer.stop should terminate immediately if no exchanges are in progress Mikhail Yankelevich
  • Re: RFR: 8304065: HttpServer.stop should terminate immediately if no exchanges are in progress Daniel Fuchs
  • Re: RFR: 8304065: HttpServer.stop should terminate immediately if no exchanges are in progress Daniel Jeliński
  • Re: RFR: 8304065: HttpServer.stop should terminate immediately if no exchanges are in progress [v2] Mikhail Yankelevich
  • Re: RFR: 8304065: HttpServer.stop should terminate immediately if no exchanges are in progress Daniel Fuchs
  • Re: RFR: 8304065: HttpServer.stop should terminate immediately if no exchanges are in progress [v2] Mikhail Yankelevich
  • Re: RFR: 8304065: HttpServer.stop should terminate immediately if no exchanges are in progress Daniel Fuchs
  • Re: RFR: 8304065: HttpServer.stop should terminate immediately if no exchanges are in progress [v3] Mikhail Yankelevich
  • Re: RFR: 8304065: HttpServer.stop should terminate immediately if no exchanges are in progress Daniel Fuchs
  • Re: RFR: 8304065: HttpServer.stop should terminate immediately if no exchanges are in progress Daniel Jeliński
  • Re: RFR: 8304065: HttpServer.stop should terminate immediately if no exchanges are in progress [v2] Mikhail Yankelevich
  • Re: RFR: 8304065: HttpServer.stop should terminate immediately if no exchanges are in progress [v2] Mikhail Yankelevich
  • Re: RFR: 8304065: HttpServer.stop should terminate immediately if no exchanges are in progress [v3] Mikhail Yankelevich
  • Re: RFR: 8304065: HttpServer.stop should terminate immediately if no exchanges are in progress [v3] Daniel Fuchs
  • Re: RFR: 8304065: HttpServer.stop should terminate immediately if no exchanges are in progress [v4] Mikhail Yankelevich
  • Re: RFR: 8304065: HttpServer.stop should terminate immediately if no exchanges are in progress [v4] Mark Sheppard
  • Re: RFR: 8304065: HttpServer.stop should terminate immediately if no exchanges are in progress [v4] Mikhail Yankelevich
  • Re: RFR: 8304065: HttpServer.stop should terminate immediately if no exchanges are in progress [v4] Mark Sheppard
  • Re: RFR: 8304065: HttpServer.stop should terminate immediately if no exchanges are in progress [v4] Daniel Fuchs
  • Re: RFR: 8304065: HttpServer.stop should terminate immediately if no exchanges are in progress [v4] Daniel Fuchs
  • Re: RFR: 8304065: HttpServer.stop should terminate immediately if no exchanges are in progress [v4] Daniel Fuchs
  • Re: RFR: 8304065: HttpServer.stop should terminate immediately if no exchanges are in progress [v4] Mark Sheppard
  • Re: RFR: 8304065: HttpServer.stop should terminate immediately if no exchanges are in progress [v4] Michael McMahon
  • Re: RFR: 8304065: HttpServer.stop should terminate immediately if no exchanges are in progress [v4] Mark Sheppard
  • Re: RFR: 8304065: HttpServer.stop should terminate immediately if no exchanges are in progress [v4] Mark Sheppard
  • Re: RFR: 8304065: HttpServer.stop should terminate immediately if no exchanges are in progress [v4] Daniel Fuchs
  • Re: RFR: 8304065: HttpServer.stop should terminate immediately if no exchanges are in progress [v4] Michael McMahon
  • Re: RFR: 8304065: HttpServer.stop should terminate immediately if no exchanges are in progress [v4] Daniel Fuchs
  • Re: RFR: 8304065: HttpServer.stop should terminate immediately if no exchanges are in progress [v4] Michael McMahon
  • Re: RFR: 8304065: HttpServer.stop should terminate immediately if no exchanges are in progress [v4] Mikhail Yankelevich
  • Re: RFR: 8304065: HttpServer.stop should terminate immediately if no exchanges are in progress [v5] Mikhail Yankelevich
  • Re: RFR: 8304065: HttpServer.stop should terminate immediately if no exchanges are in progress [v5] Mark Sheppard
  • Re: RFR: 8304065: HttpServer.stop should terminate immediately if no exchanges are in progress [v5] Daniel Fuchs
  • Re: RFR: 8304065: HttpServer.stop should terminate immediately if no exchanges are in progress [v5] Daniel Fuchs
  • Re: RFR: 8304065: HttpServer.stop should terminate immediately if no exchanges are in progress [v6] Mikhail Yankelevich
  • Re: RFR: 8304065: HttpServer.stop should terminate immediately if no exchanges are in progress [v6] Daniel Fuchs
  • Re: RFR: 8304065: HttpServer.stop should terminate immediately if no exchanges are in progress [v6] duke
  • Re: RFR: 8304065: HttpServer.stop should terminate immediately if no exchanges are in progress [v6] Michael McMahon
  • Integrated: 8304065: HttpServer.stop should terminate immediately if no exchanges are in progress Mikhail Yankelevich
• RFR: 8357268: Use JavaNioAccess.getBufferAddress rather than DirectBuffer.address() Per Minborg
  • Re: RFR: 8357268: Use JavaNioAccess.getBufferAddress rather than DirectBuffer.address() Per Minborg
  • Re: RFR: 8357268: Use JavaNioAccess.getBufferAddress rather than DirectBuffer.address() [v7] Valerie Peng
  • Re: RFR: 8357268: Use JavaNioAccess.getBufferAddress rather than DirectBuffer.address() [v7] Valerie Peng
  • Re: RFR: 8357268: Use JavaNioAccess.getBufferAddress rather than DirectBuffer.address() Alan Bateman
  • Re: RFR: 8357268: Use JavaNioAccess.getBufferAddress rather than DirectBuffer.address() [v2] Per Minborg
  • Re: RFR: 8357268: Use JavaNioAccess.getBufferAddress rather than DirectBuffer.address() [v3] Per Minborg
  • Re: RFR: 8357268: Use JavaNioAccess.getBufferAddress rather than DirectBuffer.address() [v3] Alan Bateman
  • Re: RFR: 8357268: Use JavaNioAccess.getBufferAddress rather than DirectBuffer.address() [v3] Valerie Peng
  • Re: RFR: 8357268: Use JavaNioAccess.getBufferAddress rather than DirectBuffer.address() [v3] Alan Bateman
  • Re: RFR: 8357268: Use JavaNioAccess.getBufferAddress rather than DirectBuffer.address() [v3] Per Minborg
  • Re: RFR: 8357268: Use JavaNioAccess.getBufferAddress rather than DirectBuffer.address() [v3] Alan Bateman
  • Re: RFR: 8357268: Use JavaNioAccess.getBufferAddress rather than DirectBuffer.address() [v4] Per Minborg
  • Re: RFR: 8357268: Use JavaNioAccess.getBufferAddress rather than DirectBuffer.address() [v5] Per Minborg
  • Re: RFR: 8357268: Use JavaNioAccess.getBufferAddress rather than DirectBuffer.address() [v5] Shaojin Wen
  • Re: RFR: 8357268: Use JavaNioAccess.getBufferAddress rather than DirectBuffer.address() [v5] Shaojin Wen
  • Re: RFR: 8357268: Use JavaNioAccess.getBufferAddress rather than DirectBuffer.address() [v5] Valerie Peng
  • Re: RFR: 8357268: Use JavaNioAccess.getBufferAddress rather than DirectBuffer.address() [v5] Valerie Peng
  • Re: RFR: 8357268: Use JavaNioAccess.getBufferAddress rather than DirectBuffer.address() [v6] Per Minborg
  • Re: RFR: 8357268: Use JavaNioAccess.getBufferAddress rather than DirectBuffer.address() [v7] Per Minborg
  • Re: RFR: 8357268: Use JavaNioAccess.getBufferAddress rather than DirectBuffer.address() [v7] Valerie Peng
  • Re: RFR: 8357268: Use JavaNioAccess.getBufferAddress rather than DirectBuffer.address() [v7] Alan Bateman
  • Re: RFR: 8357268: Use JavaNioAccess.getBufferAddress rather than DirectBuffer.address() [v7] Alan Bateman
  • Re: RFR: 8357268: Use JavaNioAccess.getBufferAddress rather than DirectBuffer.address() [v7] Per Minborg
  • Re: RFR: 8357268: Use JavaNioAccess.getBufferAddress rather than DirectBuffer.address() [v7] Alan Bateman
  • Re: RFR: 8357268: Use JavaNioAccess.getBufferAddress rather than DirectBuffer.address() [v8] Per Minborg
  • Re: RFR: 8357268: Use JavaNioAccess.getBufferAddress rather than DirectBuffer.address() [v8] Alan Bateman
  • Re: RFR: 8357268: Use JavaNioAccess.getBufferAddress rather than DirectBuffer.address() [v8] Per Minborg
  • Re: RFR: 8357268: Use JavaNioAccess.getBufferAddress rather than DirectBuffer.address() [v9] Per Minborg
  • Re: RFR: 8357268: Use JavaNioAccess.getBufferAddress rather than DirectBuffer.address() [v10] Per Minborg
  • Re: RFR: 8357268: Use JavaNioAccess.getBufferAddress rather than DirectBuffer.address() [v10] Alan Bateman
  • Re: RFR: 8357268: Use JavaNioAccess.getBufferAddress rather than DirectBuffer.address() [v10] Per Minborg
  • Re: RFR: 8357268: Use JavaNioAccess.getBufferAddress rather than DirectBuffer.address() [v11] Per Minborg
  • Re: RFR: 8357268: Use JavaNioAccess.getBufferAddress rather than DirectBuffer.address() [v11] Alan Bateman
  • Integrated: 8357268: Use JavaNioAccess.getBufferAddress rather than DirectBuffer.address() Per Minborg
• RFR: 8356632: Fix remaining {@link/@linkplain} tags with refer to private/protected types in java.base Nizar Benalla
  • Re: RFR: 8356632: Fix remaining {@link/@linkplain} tags with refer to private/protected types in java.base Chen Liang
  • Re: RFR: 8356632: Fix remaining {@link/@linkplain} tags with refer to private/protected types in java.base Nizar Benalla
  • Re: RFR: 8356632: Fix remaining {@link/@linkplain} tags with refer to private/protected types in java.base Joe Darcy
  • Re: RFR: 8356632: Fix remaining {@link/@linkplain} tags with refer to private/protected types in java.base Nizar Benalla
  • Re: RFR: 8356632: Fix remaining {@link/@linkplain} tags with refer to private/protected types in java.base ExE Boss
  • Re: RFR: 8356632: Fix remaining {@link/@linkplain} tags with refer to private/protected types in java.base Alan Bateman
  • Re: RFR: 8356632: Fix remaining {@link/@linkplain} tags with refer to private/protected types in java.base Alan Bateman
  • Re: RFR: 8356632: Fix remaining {@link/@linkplain} tags with refer to private/protected types in java.base Daniel Fuchs
  • Re: RFR: 8356632: Fix remaining {@link/@linkplain} tags with refer to private/protected types in java.base [v2] Nizar Benalla
  • Re: RFR: 8356632: Fix remaining {@link/@linkplain} tags with refer to private/protected types in java.base [v2] Chen Liang
  • Re: RFR: 8356632: Fix remaining {@link/@linkplain} tags with refer to private/protected types in java.base [v2] Weijun Wang
  • Re: RFR: 8356632: Fix remaining {@link/@linkplain} tags with refer to private/protected types in java.base [v3] Nizar Benalla
  • Re: RFR: 8356632: Fix remaining {@link/@linkplain} tags with refer to private/protected types in java.base [v3] Weijun Wang
  • Re: RFR: 8356632: Fix remaining {@link/@linkplain} tags with refer to private/protected types in java.base [v3] Nizar Benalla
  • Integrated: 8356632: Fix remaining {@link/@linkplain} tags with refer to private/protected types in java.base Nizar Benalla
• Integrated: 8351843: change test/jdk/com/sun/net/httpserver/simpleserver/RootDirPermissionsTest.java to a manual test serhiysachkov
• Re: RFR: 8348986: Improve coverage of enhanced exception messages [v10] Michael McMahon
  • Re: RFR: 8348986: Improve coverage of enhanced exception messages [v10] Daniel Fuchs
• Re: RFR: 8351843: change test/jdk/com/sun/net/httpserver/simpleserver/RootDirPermissionsTest.java to a manual test [v2] serhiysachkov
  • Re: RFR: 8351843: change test/jdk/com/sun/net/httpserver/simpleserver/RootDirPermissionsTest.java to a manual test [v2] Daniel Fuchs
  • Re: RFR: 8351843: change test/jdk/com/sun/net/httpserver/simpleserver/RootDirPermissionsTest.java to a manual test [v2] duke
  • Re: RFR: 8351843: change test/jdk/com/sun/net/httpserver/simpleserver/RootDirPermissionsTest.java to a manual test [v2] Jaikiran Pai
• RFR: 8357013: Optimize response code parsing in HttpURLConnection Patrick Strawderman
  • Re: RFR: 8357013: Optimize response code parsing in HttpURLConnection Daniel Fuchs
  • Re: RFR: 8357013: Optimize response code parsing in HttpURLConnection Patrick Strawderman
  • Re: RFR: 8357013: Optimize response code parsing in HttpURLConnection Daniel Fuchs
  • Re: RFR: 8357013: Optimize response code parsing in HttpURLConnection Daniel Fuchs
  • Re: RFR: 8357013: HttpURLConnection#getResponseCode can avoid substring call when parsing to int duke
  • Integrated: 8357013: HttpURLConnection#getResponseCode can avoid substring call when parsing to int Patrick Strawderman
• The default HttpServer Executor Josiah Noel
  • Re: The default HttpServer Executor Daniel Fuchs
  • Re: The default HttpServer Executor Josiah Noel
  • Re: The default HttpServer Executor Ethan McCue
  • Re: [External] : Re: The default HttpServer Executor Daniel Fuchs
  • Re: [External] : Re: The default HttpServer Executor Josiah Noel
• Integrated: 8354024: [JMH] Create ephemeral UnixDomainSocketAddress provider with thread-safe close semantics Volkan Yazici
• RFR: 8351347: HttpClient Improve logging of response headers Volkan Yazici
  • Re: RFR: 8351347: HttpClient Improve logging of response headers Daniel Fuchs
  • Re: RFR: 8351347: HttpClient Improve logging of response headers Volkan Yazici
  • Re: RFR: 8351347: HttpClient Improve logging of response headers Volkan Yazici
  • Re: RFR: 8351347: HttpClient Improve logging of response headers [v2] Volkan Yazici
  • Re: RFR: 8351347: HttpClient Improve logging of response headers [v2] Daniel Fuchs
  • Re: RFR: 8351347: HttpClient Improve logging of response headers [v2] Volkan Yazici
  • Re: RFR: 8351347: HttpClient Improve logging of response headers [v2] Volkan Yazici
  • Re: RFR: 8351347: HttpClient Improve logging of response headers [v3] Volkan Yazici
  • Re: RFR: 8351347: HttpClient Improve logging of response headers [v3] Volkan Yazici
  • Re: RFR: 8351347: HttpClient Improve logging of response headers [v3] Daniel Fuchs
  • Re: RFR: 8351347: HttpClient Improve logging of response headers [v3] Michael McMahon
  • Re: RFR: 8351347: HttpClient Improve logging of response headers [v3] duke
  • Re: RFR: 8351347: HttpClient Improve logging of response headers [v3] Volkan Yazici
  • Integrated: 8351347: HttpClient Improve logging of response headers Volkan Yazici
• Re: RFR: 8354024: [JMH] Create ephemeral UnixDomainSocketAddress provider with thread-safe close semantics [v6] Volkan Yazici
  • Re: RFR: 8354024: [JMH] Create ephemeral UnixDomainSocketAddress provider with thread-safe close semantics [v6] Michael McMahon
  • Re: RFR: 8354024: [JMH] Create ephemeral UnixDomainSocketAddress provider with thread-safe close semantics [v6] duke
• Re: RFR: 8354024: [JMH] Create ephemeral UnixDomainSocketAddress provider with thread-safe close semantics [v5] Volkan Yazici
• Integrated: 8353642: Deprecate URL::getPermission method and networking permission classes for removal Daniel Fuchs
• RFR: 8353113: Peer supported certificate signature algorithms are not being checked with default SunX509 key manager Artur Barashev
  • Re: RFR: 8353113: Peer supported certificate signature algorithms are not being checked with default SunX509 key manager [v2] Artur Barashev
  • Re: RFR: 8353113: Peer supported certificate signature algorithms are not being checked with default SunX509 key manager [v3] Artur Barashev
  • Re: RFR: 8353113: Peer supported certificate signature algorithms are not being checked with default SunX509 key manager [v3] Hai-May Chao
  • Re: RFR: 8353113: Peer supported certificate signature algorithms are not being checked with default SunX509 key manager [v3] Artur Barashev
  • Re: RFR: 8353113: Peer supported certificate signature algorithms are not being checked with default SunX509 key manager [v3] Sean Mullan
  • Re: RFR: 8353113: Peer supported certificate signature algorithms are not being checked with default SunX509 key manager [v3] Hai-May Chao
  • Re: RFR: 8359956: Support algorithm constraints and certificate checks in SunX509 key manager [v3] Artur Barashev
  • Re: RFR: 8353113: Peer supported certificate signature algorithms are not being checked with default SunX509 key manager [v4] Artur Barashev
  • Re: RFR: 8353113: Peer supported certificate signature algorithms are not being checked with default SunX509 key manager [v4] Sean Mullan
  • Re: RFR: 8353113: Peer supported certificate signature algorithms are not being checked with default SunX509 key manager [v4] Artur Barashev
  • Re: RFR: 8353113: Peer supported certificate signature algorithms are not being checked with default SunX509 key manager [v4] Artur Barashev
  • Re: RFR: 8353113: Peer supported certificate signature algorithms are not being checked with default SunX509 key manager [v4] Sean Mullan
  • Re: RFR: 8353113: Peer supported certificate signature algorithms are not being checked with default SunX509 key manager [v4] Artur Barashev
  • Re: RFR: 8353113: Peer supported certificate signature algorithms are not being checked with default SunX509 key manager [v4] Sean Mullan
  • Re: RFR: 8359956: Support algorithm constraints and certificate checks in SunX509 key manager [v4] Artur Barashev
  • Re: RFR: 8353113: Peer supported certificate signature algorithms are not being checked with default SunX509 key manager [v4] Artur Barashev
  • Re: RFR: 8353113: Peer supported certificate signature algorithms are not being checked with default SunX509 key manager [v4] Sean Mullan
  • Re: RFR: 8353113: Peer supported certificate signature algorithms are not being checked with default SunX509 key manager [v4] Artur Barashev
  • Re: RFR: 8353113: Peer supported certificate signature algorithms are not being checked with default SunX509 key manager [v4] Artur Barashev
  • Re: RFR: 8353113: Peer supported certificate signature algorithms are not being checked with default SunX509 key manager [v4] Artur Barashev
  • Re: RFR: 8353113: Peer supported certificate signature algorithms are not being checked with default SunX509 key manager [v5] Artur Barashev
  • Re: RFR: 8353113: Peer supported certificate signature algorithms are not being checked with default SunX509 key manager [v6] Artur Barashev
  • Re: RFR: 8359956: Support algorithm constraints and certificate checks in SunX509 key manager [v7] Artur Barashev
  • Re: RFR: 8359956: Support algorithm constraints and certificate checks in SunX509 key manager [v8] Artur Barashev
  • Re: RFR: 8359956: Support algorithm constraints and certificate checks in SunX509 key manager [v9] Artur Barashev
  • Re: RFR: 8359956: Support algorithm constraints and certificate checks in SunX509 key manager [v9] Sean Mullan
  • Re: RFR: 8359956: Support algorithm constraints and certificate checks in SunX509 key manager [v9] Artur Barashev
  • Re: RFR: 8359956: Support algorithm constraints and certificate checks in SunX509 key manager [v9] Sean Mullan
  • Re: RFR: 8359956: Support algorithm constraints and certificate checks in SunX509 key manager [v10] Artur Barashev
  • Re: RFR: 8359956: Support algorithm constraints and certificate checks in SunX509 key manager [v11] Artur Barashev
  • Re: RFR: 8359956: Support algorithm constraints and certificate checks in SunX509 key manager [v12] Artur Barashev
  • Re: RFR: 8359956: Support algorithm constraints and certificate checks in SunX509 key manager [v13] Artur Barashev
  • Re: RFR: 8359956: Support algorithm constraints and certificate checks in SunX509 key manager [v13] Sean Mullan
  • Re: RFR: 8359956: Support algorithm constraints and certificate checks in SunX509 key manager [v13] Artur Barashev
  • Re: RFR: 8359956: Support algorithm constraints and certificate checks in SunX509 key manager [v13] Sean Mullan
  • Re: RFR: 8359956: Support algorithm constraints and certificate checks in SunX509 key manager [v13] Artur Barashev
  • Re: RFR: 8359956: Support algorithm constraints and certificate checks in SunX509 key manager [v13] Artur Barashev
  • Re: RFR: 8359956: Support algorithm constraints and certificate checks in SunX509 key manager [v13] Artur Barashev
  • Re: RFR: 8359956: Support algorithm constraints and certificate checks in SunX509 key manager [v14] Artur Barashev
  • Re: RFR: 8359956: Support algorithm constraints and certificate checks in SunX509 key manager [v14] Sean Mullan
  • Re: RFR: 8359956: Support algorithm constraints and certificate checks in SunX509 key manager [v14] Artur Barashev
  • Re: RFR: 8359956: Support algorithm constraints and certificate checks in SunX509 key manager [v14] Artur Barashev
  • Re: RFR: 8359956: Support algorithm constraints and certificate checks in SunX509 key manager [v14] Sean Mullan
  • Re: RFR: 8359956: Support algorithm constraints and certificate checks in SunX509 key manager [v14] Artur Barashev
  • Re: RFR: 8359956: Support algorithm constraints and certificate checks in SunX509 key manager [v14] Artur Barashev
  • Re: RFR: 8359956: Support algorithm constraints and certificate checks in SunX509 key manager [v14] Sean Mullan
  • Re: RFR: 8359956: Support algorithm constraints and certificate checks in SunX509 key manager [v14] Artur Barashev
  • Re: RFR: 8359956: Support algorithm constraints and certificate checks in SunX509 key manager [v14] Artur Barashev
  • Re: RFR: 8359956: Support algorithm constraints and certificate checks in SunX509 key manager [v14] Sean Mullan
  • Re: RFR: 8359956: Support algorithm constraints and certificate checks in SunX509 key manager [v14] Artur Barashev
  • Re: RFR: 8359956: Support algorithm constraints and certificate checks in SunX509 key manager [v15] Artur Barashev
  • Re: RFR: 8359956: Support algorithm constraints and certificate checks in SunX509 key manager [v15] Sean Mullan
  • Re: RFR: 8359956: Support algorithm constraints and certificate checks in SunX509 key manager [v15] Hao Sun
  • Re: RFR: 8359956: Support algorithm constraints and certificate checks in SunX509 key manager [v15] Artur Barashev
  • Integrated: 8359956: Support algorithm constraints and certificate checks in SunX509 key manager Artur Barashev
• Re: RFR: 8354024: [JMH] Create ephemeral UnixDomainSocketAddress provider with thread-safe close semantics [v4] Volkan Yazici
  • Re: RFR: 8354024: [JMH] Create ephemeral UnixDomainSocketAddress provider with thread-safe close semantics [v4] Michael McMahon
  • Re: RFR: 8354024: [JMH] Create ephemeral UnixDomainSocketAddress provider with thread-safe close semantics [v4] Volkan Yazici
• Re: RFR: 8354024: [JMH] Create ephemeral UnixDomainSocketAddress provider with thread-safe close semantics [v3] Volkan Yazici
• RFR: 8356644: Update encoding declaration to UTF-8 Magnus Ihse Bursie
  • Re: RFR: 8356644: Update encoding declaration to UTF-8 Daniel Fuchs
  • Re: RFR: 8356644: Update encoding declaration to UTF-8 Phil Race
  • Re: RFR: 8356644: Update encoding declaration to UTF-8 Naoto Sato
  • Re: RFR: 8356644: Update encoding declaration to UTF-8 Sergey Bylokhov
  • Re: RFR: 8356644: Update encoding declaration to UTF-8 Magnus Ihse Bursie
  • Re: RFR: 8356644: Update encoding declaration to UTF-8 Sergey Bylokhov

• Earlier messages
• Later messages