net-dev  

Messages by Thread

• • Re: RFR: 8344446: Remove security manager dependency from module jdk.sctp [v2] Sean Mullan
  • Re: RFR: 8344446: Remove security manager dependency from module jdk.sctp [v2] Brian Burkhalter
  • Re: RFR: 8344446: Remove security manager dependency from module jdk.sctp [v3] Brian Burkhalter
  • Re: RFR: 8344446: Remove security manager dependency from module jdk.sctp [v3] Sean Mullan
  • Integrated: 8344446: Remove security manager dependency from module jdk.sctp Brian Burkhalter
  • Re: RFR: 8344446: Remove security manager dependency from module jdk.sctp Sean Mullan
  • Re: RFR: 8344446: Remove security manager dependency from module jdk.sctp [v2] Brian Burkhalter
• SNI not sent with Java 22+ using java.net.http.HttpClient.Builder#sslParameters Nicolas Henneaux
  • Re: SNI not sent with Java 22+ using java.net.http.HttpClient.Builder#sslParameters Nicolas Henneaux
  • Re: SNI not sent with Java 22+ using java.net.http.HttpClient.Builder#sslParameters Daniel Fuchs
  • Re: SNI not sent with Java 22+ using java.net.http.HttpClient.Builder#sslParameters Nicolas Henneaux
  • Re: SNI not sent with Java 22+ using java.net.http.HttpClient.Builder#sslParameters Jaikiran Pai
  • Re: SNI not sent with Java 22+ using java.net.http.HttpClient.Builder#sslParameters Jaikiran Pai
  • Re: SNI not sent with Java 22+ using java.net.http.HttpClient.Builder#sslParameters Jaikiran Pai
  • Re: SNI not sent with Java 22+ using java.net.http.HttpClient.Builder#sslParameters Jaikiran Pai
• Integrated: 8344056: Use markdown format for man pages Magnus Ihse Bursie
• RFR: 8343150: Remove URLClassLoader.getPermissions after JEP 486 integration Jaikiran Pai
  • Re: RFR: 8343150: Remove URLClassLoader.getPermissions after JEP 486 integration Jaikiran Pai
  • Re: RFR: 8343150: Remove URLClassLoader.getPermissions after JEP 486 integration Michael McMahon
  • Re: RFR: 8343150: Remove URLClassLoader.getPermissions after JEP 486 integration [v2] Jaikiran Pai
  • Re: RFR: 8343150: Remove URLClassLoader.getPermissions after JEP 486 integration [v2] Michael McMahon
  • Re: RFR: 8343150: Remove URLClassLoader.getPermissions after JEP 486 integration [v2] Jaikiran Pai
  • Re: RFR: 8343150: Remove URLClassLoader.getPermissions after JEP 486 integration [v3] Jaikiran Pai
  • Re: RFR: 8343150: Remove URLClassLoader.getPermissions after JEP 486 integration [v3] Daniel Fuchs
  • Re: RFR: 8343150: Change URLClassLoader.getPermissions to return empty PermissionCollection [v3] Jaikiran Pai
  • Re: RFR: 8343150: Change URLClassLoader.getPermissions to return empty PermissionCollection [v3] Jaikiran Pai
  • Re: RFR: 8343150: Change URLClassLoader.getPermissions to return empty PermissionCollection [v4] Jaikiran Pai
  • Re: RFR: 8343150: Change URLClassLoader.getPermissions to return empty PermissionCollection [v4] Daniel Fuchs
  • Re: RFR: 8343150: Change URLClassLoader.getPermissions to return empty PermissionCollection [v4] Alan Bateman
  • Re: RFR: 8343150: Change URLClassLoader.getPermissions to return empty PermissionCollection [v4] Jaikiran Pai
  • Integrated: 8343150: Change URLClassLoader.getPermissions to return empty PermissionCollection Jaikiran Pai
• Re: JDK-8019345, RFC3986, RFC2396 and java.net.URI Peter Firmstone
• RFR: 8344218: Remove calls to SecurityManager and and doPrivileged in java.net.NetworkInterface after JEP 486 integration Eirik Bjørsnøs
  • Re: RFR: 8344218: Remove calls to SecurityManager and and doPrivileged in java.net.NetworkInterface after JEP 486 integration Alan Bateman
  • Re: RFR: 8344218: Remove calls to SecurityManager and and doPrivileged in java.net.NetworkInterface after JEP 486 integration [v2] Eirik Bjørsnøs
  • Re: RFR: 8344218: Remove calls to SecurityManager and and doPrivileged in java.net.NetworkInterface after JEP 486 integration [v2] Alan Bateman
  • Re: RFR: 8344218: Remove calls to SecurityManager and and doPrivileged in java.net.NetworkInterface after JEP 486 integration [v2] Eirik Bjørsnøs
  • Re: RFR: 8344218: Remove calls to SecurityManager and and doPrivileged in java.net.NetworkInterface after JEP 486 integration [v2] Daniel Fuchs
  • Re: RFR: 8344218: Remove calls to SecurityManager and and doPrivileged in java.net.NetworkInterface after JEP 486 integration [v2] Daniel Fuchs
  • Integrated: 8344218: Remove calls to SecurityManager and and doPrivileged in java.net.NetworkInterface after JEP 486 integration Eirik Bjørsnøs
• Re: RFR: 8344191: Build code should not have classpath exception David Holmes
• Integrated: 8344233: Remove calls to SecurityManager and doPrivileged in java.net.ProxySelector and sun.net.spi.DefaultProxySelector after JEP 486 integration Jaikiran Pai
• Re: RFR: 8344186: Cleanup sun.net.www.MimeTable after JEP 486 integration Jaikiran Pai
• Re: RFR: 8344233: Remove calls to SecurityManager and doPrivileged in java.net.ProxySelector and sun.net.spi.DefaultProxySelector after JEP 486 integration [v2] Jaikiran Pai
  • Re: RFR: 8344233: Remove calls to SecurityManager and doPrivileged in java.net.ProxySelector and sun.net.spi.DefaultProxySelector after JEP 486 integration [v2] Daniel Fuchs
  • Re: RFR: 8344233: Remove calls to SecurityManager and doPrivileged in java.net.ProxySelector and sun.net.spi.DefaultProxySelector after JEP 486 integration [v2] Jaikiran Pai
• Integrated: 8344186: Cleanup sun.net.www.MimeTable after JEP 486 integration Jaikiran Pai
• Re: RFR: 8342811: java/net/httpclient/PlainProxyConnectionTest.java failed: Unexpected connection count: 5 [v3] duke
• Integrated: 8342811: java/net/httpclient/PlainProxyConnectionTest.java failed: Unexpected connection count: 5 Volkan Yazıcı
• Integrated: 8344216: Remove calls to SecurityManager and and doPrivileged in java.net.Authenticator, java.net.CookieHandler, and java.net.ResponseCache after JEP 486 integration Eirik Bjørsnøs
• Integrated: 8344189: Cleanup code in sun.net.www.protocol.mailto.MailToURLConnection and sun.net.smtp after JEP 486 integration Eirik Bjørsnøs
• RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs Volkan Yazıcı
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v2] Volkan Yazıcı
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v2] Alan Bateman
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v3] Volkan Yazıcı
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v3] Alan Bateman
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v3] Daniel Fuchs
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v3] Daniel Fuchs
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v3] Volkan Yazıcı
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v3] Volkan Yazıcı
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v4] Volkan Yazıcı
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v4] Alan Bateman
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v4] Alan Bateman
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v4] Volkan Yazıcı
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v4] Volkan Yazıcı
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v4] Alan Bateman
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v4] Volkan Yazıcı
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v4] Volkan Yazıcı
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v4] Alan Bateman
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v4] Volkan Yazıcı
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v4] Volkan Yazıcı
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v4] Alan Bateman
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v4] Volkan Yazıcı
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v5] Volkan Yazıcı
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v7] Volkan Yazıcı
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v6] Volkan Yazıcı
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v8] Volkan Yazıcı
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v9] Volkan Yazıcı
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v9] Alan Bateman
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v9] Volkan Yazıcı
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v10] Volkan Yazıcı
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v10] Alan Bateman
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v10] Volkan Yazıcı
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v10] Volkan Yazıcı
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v11] Volkan Yazıcı
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v11] Alan Bateman
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v11] Volkan Yazıcı
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v12] Volkan Yazıcı
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v12] Daniel Fuchs
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v12] Mark Sheppard
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v12] Volkan Yazıcı
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v12] Mark Sheppard
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v12] Volkan Yazıcı
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v12] Mark Sheppard
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v13] Volkan Yazıcı
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v13] Daniel Fuchs
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v13] Mark Sheppard
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v13] Volkan Yazıcı
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v13] Mark Sheppard
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v13] Mark Sheppard
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v13] Alan Bateman
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v13] Volkan Yazıcı
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v14] Volkan Yazıcı
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v14] Alan Bateman
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v14] Volkan Yazıcı
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v14] Alan Bateman
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v14] Volkan Yazıcı
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v15] Volkan Yazıcı
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v16] Volkan Yazıcı
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v16] Volkan Yazıcı
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v16] Daniel Fuchs
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v16] Volkan Yazıcı
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v16] Daniel Fuchs
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v17] Volkan Yazıcı
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v17] Alan Bateman
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v17] Volkan Yazıcı
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v17] Volkan Yazıcı
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v17] Alan Bateman
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v17] Volkan Yazıcı
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v18] Volkan Yazıcı
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v19] Volkan Yazıcı
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v19] Daniel Fuchs
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v19] Volkan Yazıcı
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v20] Volkan Yazıcı
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v21] Volkan Yazıcı
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v22] Volkan Yazıcı
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v22] Alan Bateman
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v22] Daniel Fuchs
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v22] Alan Bateman
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v22] Volkan Yazıcı
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v22] Alan Bateman
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v22] Volkan Yazıcı
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v22] Alan Bateman
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v22] Volkan Yazıcı
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v22] Volkan Yazıcı
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v22] Alan Bateman
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v22] Daniel Fuchs
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v22] Volkan Yazıcı
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v22] Volkan Yazıcı
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v22] Alan Bateman
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v22] Volkan Yazıcı
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v22] Daniel Fuchs
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v22] Volkan Yazıcı
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v22] Daniel Fuchs
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v22] Volkan Yazıcı
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v23] Volkan Yazıcı
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v23] Daniel Fuchs
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v23] Alan Bateman
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v23] Volkan Yazıcı
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v23] Alan Bateman
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v23] Volkan Yazıcı
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v23] Alan Bateman
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v23] Volkan Yazıcı
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v23] Volkan Yazıcı
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v24] Volkan Yazıcı
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v25] Volkan Yazıcı
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v26] Volkan Yazıcı
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v26] Daniel Fuchs
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v26] Volkan Yazıcı
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v26] Alan Bateman
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v26] Volkan Yazıcı
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v27] Volkan Yazıcı
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v27] Volkan Yazıcı
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v27] Alan Bateman
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v27] Daniel Fuchs
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v27] duke
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v27] Jaikiran Pai
  • Integrated: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs Volkan Yazıcı
• RFR: 8344221: Remove calls to SecurityManager and and doPrivileged in java.net.IDN, java.net.URL, java.net.URLConnection, sun.net.util.URLUtil, and java.net.URLStreamHandlerProvider after JEP 486 integration Daniel Fuchs
  • Re: RFR: 8344221: Remove calls to SecurityManager and and doPrivileged in java.net.IDN, java.net.URL, java.net.URLConnection, sun.net.util.URLUtil, and java.net.URLStreamHandlerProvider after JEP 486 integration Alan Bateman
  • Re: RFR: 8344221: Remove calls to SecurityManager and and doPrivileged in java.net.IDN, java.net.URL, java.net.URLConnection, sun.net.util.URLUtil, and java.net.URLStreamHandlerProvider after JEP 486 integration Daniel Fuchs
  • Re: RFR: 8344221: Remove calls to SecurityManager and and doPrivileged in java.net.IDN, java.net.URL, java.net.URLConnection, sun.net.util.URLUtil, and java.net.URLStreamHandlerProvider after JEP 486 integration [v2] Roger Riggs
  • Re: RFR: 8344221: Remove calls to SecurityManager and and doPrivileged in java.net.IDN, java.net.URL, java.net.URLConnection, sun.net.util.URLUtil, and java.net.URLStreamHandlerProvider after JEP 486 integration [v2] Daniel Fuchs
  • Re: RFR: 8344221: Remove calls to SecurityManager and and doPrivileged in java.net.IDN, java.net.URL, java.net.URLConnection, sun.net.util.URLUtil, and java.net.URLStreamHandlerProvider after JEP 486 integration [v2] Daniel Fuchs
  • Re: RFR: 8344221: Remove calls to SecurityManager and and doPrivileged in java.net.IDN, java.net.URL, java.net.URLConnection, sun.net.util.URLUtil, and java.net.URLStreamHandlerProvider after JEP 486 integration [v3] Daniel Fuchs
  • Re: RFR: 8344221: Remove calls to SecurityManager and and doPrivileged in java.net.IDN, java.net.URL, java.net.URLConnection, sun.net.util.URLUtil, and java.net.URLStreamHandlerProvider after JEP 486 integration [v3] Roger Riggs
  • Re: RFR: 8344221: Remove calls to SecurityManager and and doPrivileged in java.net.IDN, java.net.URL, java.net.URLConnection, sun.net.util.URLUtil, and java.net.URLStreamHandlerProvider after JEP 486 integration [v3] Alan Bateman
  • Re: RFR: 8344221: Remove calls to SecurityManager and and doPrivileged in java.net.IDN, java.net.URL, java.net.URLConnection, sun.net.util.URLUtil, and java.net.URLStreamHandlerProvider after JEP 486 integration [v3] Daniel Fuchs
  • Re: RFR: 8344221: Remove calls to SecurityManager and and doPrivileged in java.net.IDN, java.net.URL, java.net.URLConnection, sun.net.util.URLUtil, and java.net.URLStreamHandlerProvider after JEP 486 integration [v4] Daniel Fuchs
  • Re: RFR: 8344221: Remove calls to SecurityManager and and doPrivileged in java.net.IDN, java.net.URL, java.net.URLConnection, sun.net.util.URLUtil, and java.net.URLStreamHandlerProvider after JEP 486 integration [v4] Alan Bateman
  • Re: RFR: 8344221: Remove calls to SecurityManager and and doPrivileged in java.net.IDN, java.net.URL, java.net.URLConnection, sun.net.util.URLUtil, and java.net.URLStreamHandlerProvider after JEP 486 integration [v4] Roger Riggs
  • Integrated: 8344221: Remove calls to SecurityManager and and doPrivileged in java.net.IDN, java.net.URL, java.net.URLConnection, sun.net.util.URLUtil, and java.net.URLStreamHandlerProvider after JEP 486 integration Daniel Fuchs
• Re: RFR: 8344216: Remove calls to SecurityManager and and doPrivileged in java.net.Authenticator, java.net.CookieHandler, and java.net.ResponseCache after JEP 486 integration Eirik Bjørsnøs
  • Re: RFR: 8344216: Remove calls to SecurityManager and and doPrivileged in java.net.Authenticator, java.net.CookieHandler, and java.net.ResponseCache after JEP 486 integration Daniel Fuchs
• Re: RFR: 8344233: Remove calls to SecurityManager and doPrivileged in java.net.ProxySelector and sun.net.spi.DefaultProxySelector after JEP 486 integration Sean Mullan
  • Re: RFR: 8344233: Remove calls to SecurityManager and doPrivileged in java.net.ProxySelector and sun.net.spi.DefaultProxySelector after JEP 486 integration Jaikiran Pai
  • Re: RFR: 8344233: Remove calls to SecurityManager and doPrivileged in java.net.ProxySelector and sun.net.spi.DefaultProxySelector after JEP 486 integration Jaikiran Pai
• Re: RFR: 8344056: Use markdown format for man pages [v4] Christian Stein
  • Re: RFR: 8344056: Use markdown format for man pages [v4] Iris Clark
  • Re: RFR: 8344056: Use markdown format for man pages [v4] Eirik Bjørsnøs
  • Re: RFR: 8344056: Use markdown format for man pages [v4] Magnus Ihse Bursie
• RFR: 8344315: Clean up sun.net.www.protocol.jrt.JavaRuntimeURLConnection after JEP 486 integration Jaikiran Pai
  • Re: RFR: 8344315: Clean up sun.net.www.protocol.jrt.JavaRuntimeURLConnection after JEP 486 integration Daniel Fuchs
  • Re: RFR: 8344315: Clean up sun.net.www.protocol.jrt.JavaRuntimeURLConnection after JEP 486 integration Alan Bateman
  • Re: RFR: 8344315: Clean up sun.net.www.protocol.jrt.JavaRuntimeURLConnection after JEP 486 integration Jaikiran Pai
  • Re: RFR: 8344315: Clean up sun.net.www.protocol.jrt.JavaRuntimeURLConnection after JEP 486 integration Alan Bateman
  • Integrated: 8344315: Clean up sun.net.www.protocol.jrt.JavaRuntimeURLConnection after JEP 486 integration Jaikiran Pai
• Re: RFR: 8344056: Use markdown format for man pages [v3] Magnus Ihse Bursie
• Integrated: 8344228: Revisit SecurityManager usage in java.net.http after JEP 486 integration Daniel Fuchs
• Re: RFR: 8344189: Cleanup code in sun.net.www.protocol.mailto.MailToURLConnection and sun.net.smtp after JEP 486 integration Daniel Fuchs

• Later messages