net-dev
Thread
Date
Earlier messages
Later messages
Messages by Thread
Re: RFR: 8353453: URLDecoder should use HexFormat
Patrick Strawderman
Integrated: 8353453: URLDecoder should use HexFormat
Patrick Strawderman
RFR: 8330598: java/net/httpclient/Http1ChunkedTest.java fails with java.util.MissingFormatArgumentException: Format specifier '%s'
serhiysachkov
Re: RFR: 8330598: java/net/httpclient/Http1ChunkedTest.java fails with java.util.MissingFormatArgumentException: Format specifier '%s'
Daniel Fuchs
Re: RFR: 8330598: java/net/httpclient/Http1ChunkedTest.java fails with java.util.MissingFormatArgumentException: Format specifier '%s'
duke
Integrated: 8330598: java/net/httpclient/Http1ChunkedTest.java fails with java.util.MissingFormatArgumentException: Format specifier '%s'
serhiysachkov
RFD: FTP fallback of the 'file:' URL scheme
Eirik Bjørsnøs
Re: RFD: FTP fallback of the 'file:' URL scheme
Alan Bateman
Re: RFD: FTP fallback of the 'file:' URL scheme
Eirik Bjørsnøs
Relaxing TLS for java.net.http.HttpClient
Pavel Rappo
Re: Relaxing TLS for java.net.http.HttpClient
Daniel Fuchs
Re: Relaxing TLS for java.net.http.HttpClient
Pavel Rappo
Re: Relaxing TLS for java.net.http.HttpClient
Michael McMahon
Re: Relaxing TLS for java.net.http.HttpClient
Pavel Rappo
RFD: Use of ~ (tilde) when considering local and non-local file URLs
Eirik Bjørsnøs
Re: RFD: Use of ~ (tilde) when considering local and non-local file URLs
Eirik Bjørsnøs
Re: RFD: Use of ~ (tilde) when considering local and non-local file URLs
Jaikiran Pai
Re: RFD: Use of ~ (tilde) when considering local and non-local file URLs
Eirik Bjørsnøs
Re: RFD: Use of ~ (tilde) when considering local and non-local file URLs
Eirik Bjørsnøs
Re: RFD: Use of ~ (tilde) when considering local and non-local file URLs
Eirik Bjørsnøs
RFR: 8352858: Make java.net.JarURLConnection fields final
Eirik Bjørsnøs
Re: RFR: 8352858: Make java.net.JarURLConnection fields final [v2]
Eirik Bjørsnøs
Re: RFR: 8352858: Make java.net.JarURLConnection fields final [v2]
Daniel Fuchs
Re: RFR: 8352858: Make java.net.JarURLConnection fields final [v2]
Daniel Fuchs
Re: RFR: 8352858: Make java.net.JarURLConnection fields final [v2]
Eirik Bjørsnøs
Re: RFR: 8352858: Make java.net.JarURLConnection fields final [v2]
Daniel Fuchs
Re: RFR: 8352858: Make java.net.JarURLConnection fields final [v2]
Eirik Bjørsnøs
Re: RFR: 8352858: Make java.net.JarURLConnection fields final [v2]
Jaikiran Pai
Re: RFR: 8352858: Make java.net.JarURLConnection fields final [v2]
Eirik Bjørsnøs
Re: RFR: 8352858: Make java.net.JarURLConnection fields final
Jaikiran Pai
Re: RFR: 8352858: Make java.net.JarURLConnection fields final [v2]
Eirik Bjørsnøs
Integrated: 8352858: Make java.net.JarURLConnection fields final
Eirik Bjørsnøs
RFR: 8352706: httpclient HeadTest does not run on HTTP2
Daniel Jeliński
Re: RFR: 8352706: httpclient HeadTest does not run on HTTP2
Michael McMahon
Integrated: 8352706: httpclient HeadTest does not run on HTTP2
Daniel Jeliński
Re: RFR: 8352706: httpclient HeadTest does not run on HTTP2
Daniel Jeliński
RFR: 8352623: MultiExchange should cancel exchange impl if responseFilters throws
Daniel Fuchs
Re: RFR: 8352623: MultiExchange should cancel exchange impl if responseFilters throws
Daniel Jeliński
Re: RFR: 8352623: MultiExchange should cancel exchange impl if responseFilters throws
Daniel Fuchs
Re: RFR: 8352623: MultiExchange should cancel exchange impl if responseFilters throws [v2]
Daniel Fuchs
Re: RFR: 8352623: MultiExchange should cancel exchange impl if responseFilters throws [v2]
Daniel Jeliński
Integrated: 8352623: MultiExchange should cancel exchange impl if responseFilters throws
Daniel Fuchs
RFR: 8350279: HttpClient: Add a new HttpResponse method to identify connections
Volkan Yazici
Re: RFR: 8350279: HttpClient: Add a new HttpResponse method to identify connections
Chen Liang
Re: RFR: 8350279: HttpClient: Add a new HttpResponse method to identify connections
Daniel Fuchs
Re: RFR: 8350279: HttpClient: Add a new HttpResponse method to identify connections
Chen Liang
Re: RFR: 8350279: HttpClient: Add a new HttpResponse method to identify connections
Daniel Fuchs
Re: RFR: 8350279: HttpClient: Add a new HttpResponse method to identify connections [v2]
Volkan Yazici
Re: RFR: 8350279: HttpClient: Add a new HttpResponse method to identify connections [v3]
Volkan Yazici
Re: RFR: 8350279: HttpClient: Add a new HttpResponse method to identify connections [v3]
Michael McMahon
Re: RFR: 8350279: HttpClient: Add a new HttpResponse method to identify connections [v3]
Daniel Fuchs
Re: RFR: 8350279: HttpClient: Add a new HttpResponse method to identify connections [v3]
Volkan Yazici
Re: RFR: 8350279: HttpClient: Add a new HttpResponse method to identify connections [v4]
Volkan Yazici
Re: RFR: 8350279: HttpClient: Add a new HttpResponse method to identify connections [v4]
Jaikiran Pai
Re: RFR: 8350279: HttpClient: Add a new HttpResponse method to identify connections [v4]
Daniel Fuchs
Re: RFR: 8350279: HttpClient: Add a new HttpResponse method to identify connections [v4]
Volkan Yazici
Re: RFR: 8350279: HttpClient: Add a new HttpResponse method to identify connections [v4]
Jaikiran Pai
Re: RFR: 8350279: HttpClient: Add a new HttpResponse method to identify connections [v4]
Daniel Fuchs
Re: RFR: 8350279: HttpClient: Add a new HttpResponse method to identify connections [v4]
Jaikiran Pai
Re: RFR: 8350279: HttpClient: Add a new HttpResponse method to identify connections [v4]
Daniel Fuchs
Re: RFR: 8350279: HttpClient: Add a new HttpResponse method to identify connections [v4]
Volkan Yazici
Re: RFR: 8350279: HttpClient: Add a new HttpResponse method to identify connections [v4]
Jaikiran Pai
Re: RFR: 8350279: HttpClient: Add a new HttpResponse method to identify connections [v4]
Daniel Fuchs
Re: RFR: 8350279: HttpClient: Add a new HttpResponse method to identify connections [v4]
Volkan Yazici
Re: RFR: 8350279: HttpClient: Add a new HttpResponse method to identify connections [v4]
Volkan Yazici
Re: RFR: 8350279: HttpClient: Add a new HttpResponse method to identify connections [v4]
Jaikiran Pai
Re: RFR: 8350279: HttpClient: Add a new HttpResponse method to identify connections [v4]
Volkan Yazici
Re: RFR: 8350279: HttpClient: Add a new HttpResponse method to identify connections [v4]
Volkan Yazici
Re: RFR: 8350279: HttpClient: Add a new HttpResponse method to identify connections [v4]
Jaikiran Pai
Re: RFR: 8350279: HttpClient: Add a new HttpResponse method to identify connections [v4]
Daniel Fuchs
Re: RFR: 8350279: HttpClient: Add a new HttpResponse method to identify connections
Daniel Fuchs
Re: RFR: 8350279: HttpClient: Add a new HttpResponse method to identify connections [v3]
Volkan Yazici
Re: RFR: 8350279: HttpClient: Add a new HttpResponse method to identify connections [v5]
Volkan Yazici
Re: RFR: 8350279: HttpClient: Add a new HttpResponse method to identify connections [v5]
Jaikiran Pai
Re: RFR: 8350279: HttpClient: Add a new HttpResponse method to identify connections [v5]
Volkan Yazici
Re: RFR: 8350279: HttpClient: Add a new HttpResponse method to identify connections [v5]
Jaikiran Pai
Re: RFR: 8350279: HttpClient: Add a new HttpResponse method to identify connections [v5]
Daniel Fuchs
Re: RFR: 8350279: HttpClient: Add a new HttpResponse method to identify connections [v5]
Volkan Yazici
Re: RFR: 8350279: HttpClient: Add a new HttpResponse method to identify connections [v5]
Jaikiran Pai
Re: RFR: 8350279: HttpClient: Add a new HttpResponse method to identify connections [v5]
Jaikiran Pai
Re: RFR: 8350279: HttpClient: Add a new HttpResponse method to identify connections [v6]
Volkan Yazici
Re: RFR: 8350279: HttpClient: Add a new HttpResponse method to identify connections [v6]
Jaikiran Pai
Re: RFR: 8350279: HttpClient: Add a new HttpResponse method to identify connections [v6]
Daniel Fuchs
Re: RFR: 8350279: HttpClient: Add a new HttpResponse method to identify connections [v6]
Jaikiran Pai
Re: RFR: 8350279: HttpClient: Add a new HttpResponse method to identify connections [v6]
Volkan Yazici
Re: RFR: 8350279: HttpClient: Add a new HttpResponse method to identify connections [v6]
Jaikiran Pai
Re: RFR: 8350279: HttpClient: Add a new HttpResponse method to identify connections [v6]
Daniel Fuchs
Re: RFR: 8350279: HttpClient: Add a new HttpResponse method to identify connections [v6]
Jaikiran Pai
Re: RFR: 8350279: HttpClient: Add a new HttpResponse method to identify connections [v6]
Volkan Yazici
Re: RFR: 8350279: HttpClient: Add a new HttpResponse method to identify connections [v6]
Volkan Yazici
Re: RFR: 8350279: HttpClient: Add a new HttpResponse method to identify connections [v6]
Jaikiran Pai
Re: RFR: 8350279: HttpClient: Add a new HttpResponse method to identify connections [v6]
Daniel Fuchs
Re: RFR: 8350279: HttpClient: Add a new HttpResponse method to identify connections [v6]
Jaikiran Pai
Re: RFR: 8350279: HttpClient: Add a new HttpResponse method to identify connections [v6]
Daniel Fuchs
Re: RFR: 8350279: HttpClient: Add a new HttpResponse method to identify connections [v6]
Volkan Yazici
Re: RFR: 8350279: HttpClient: Add a new HttpResponse method to identify connections [v7]
Volkan Yazici
Re: RFR: 8350279: HttpClient: Add a new HttpResponse method to identify connections [v7]
Jaikiran Pai
Re: RFR: 8350279: HttpClient: Add a new HttpResponse method to identify connections [v7]
Volkan Yazici
Re: RFR: 8350279: HttpClient: Add a new HttpResponse method to identify connections [v8]
Volkan Yazici
Re: RFR: 8350279: HttpClient: Add a new HttpResponse method to identify connections [v9]
Volkan Yazici
Re: RFR: 8350279: HttpClient: Add a new HttpResponse method to identify connections [v10]
Volkan Yazici
Re: RFR: 8350279: HttpClient: Add a new HttpResponse method to identify connections [v10]
Jaikiran Pai
Re: RFR: 8350279: HttpClient: Add a new HttpResponse method to identify connections [v10]
Volkan Yazici
Re: RFR: 8350279: HttpClient: Add a new HttpResponse method to identify connections [v11]
Volkan Yazici
Re: RFR: 8350279: HttpClient: Add a new HttpResponse method to identify connections [v11]
Jaikiran Pai
Re: RFR: 8350279: HttpClient: Add a new HttpResponse method to identify connections [v12]
Volkan Yazici
Re: RFR: 8350279: HttpClient: Add a new HttpResponse method to identify connections [v12]
Daniel Fuchs
Re: RFR: 8350279: HttpClient: Add a new HttpResponse method to identify connections [v12]
Daniel Fuchs
Re: RFR: 8350279: HttpClient: Add a new HttpResponse method to identify connections [v12]
Daniel Fuchs
Re: RFR: 8350279: HttpClient: Add a new HttpResponse method to identify connections [v12]
Volkan Yazici
Re: RFR: 8350279: HttpClient: Add a new HttpResponse method to identify connections [v12]
Daniel Fuchs
Re: RFR: 8350279: HttpClient: Add a new HttpResponse method to identify connections [v12]
Volkan Yazici
Re: RFR: 8350279: HttpClient: Add a new HttpResponse method to identify connections [v12]
Daniel Fuchs
Re: RFR: 8350279: HttpClient: Add a new HttpResponse method to identify connections [v12]
Daniel Fuchs
Re: RFR: 8350279: HttpClient: Add a new HttpResponse method to identify connections [v12]
Volkan Yazici
Re: RFR: 8350279: HttpClient: Add a new HttpResponse method to identify connections [v12]
Volkan Yazici
Re: RFR: 8350279: HttpClient: Add a new HttpResponse method to identify connections [v13]
Volkan Yazici
Re: RFR: 8350279: HttpClient: Add a new HttpResponse method to identify connections [v14]
Volkan Yazici
Re: RFR: 8350279: HttpClient: Add a new HttpResponse method to identify connections [v14]
Daniel Fuchs
Re: RFR: 8350279: HttpClient: Add a new HttpResponse method to identify connections [v14]
duke
Integrated: 8350279: HttpClient: Add a new HttpResponse method to identify connections
Volkan Yazici
RFR: 8351601: [JMH] test UnixSocketChannelReadWrite failed for 2 threads config
Volkan Yazici
Re: RFR: 8351601: [JMH] test UnixSocketChannelReadWrite failed for 2 threads config
Michael McMahon
Re: RFR: 8351601: [JMH] test UnixSocketChannelReadWrite failed for 2 threads config
Volkan Yazici
Re: RFR: 8351601: [JMH] test UnixSocketChannelReadWrite failed for 2 threads config
Michael McMahon
Re: RFR: 8351601: [JMH] test UnixSocketChannelReadWrite failed for 2 threads config
Volkan Yazici
Re: RFR: 8351601: [JMH] test UnixSocketChannelReadWrite failed for 2 threads config [v2]
Volkan Yazici
Re: RFR: 8351601: [JMH] test UnixSocketChannelReadWrite failed for 2 threads config [v2]
Michael McMahon
Re: RFR: 8351601: [JMH] test UnixSocketChannelReadWrite failed for 2 threads config [v3]
Volkan Yazici
Re: RFR: 8351601: [JMH] test UnixSocketChannelReadWrite failed for 2 threads config [v3]
duke
Integrated: 8351601: [JMH] test UnixSocketChannelReadWrite failed for 2 threads config
Volkan Yazici
Re: RFR: 8351601: [JMH] test UnixSocketChannelReadWrite failed for 2 threads config
Michael McMahon
Re: RFR: 8351601: [JMH] test UnixSocketChannelReadWrite failed for 2 threads config
Volkan Yazici
Re: RFR: 8351601: [JMH] test UnixSocketChannelReadWrite failed for 2 threads config
Michael McMahon
RFR: 8351843: change open/test/jdk/com/sun/net/httpserver/simpleserver/RootDirPermissionsTest.java to a manual test
serhiysachkov
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
Integrated: 8351843: change test/jdk/com/sun/net/httpserver/simpleserver/RootDirPermissionsTest.java to a manual test
serhiysachkov
RFR: 8351339: WebSocket::sendBinary assume that user supplied buffers are BIG_ENDIAN
Volkan Yazici
Re: RFR: 8351339: WebSocket::sendBinary assume that user supplied buffers are BIG_ENDIAN [v2]
Volkan Yazici
Re: RFR: 8351339: WebSocket::sendBinary assume that user supplied buffers are BIG_ENDIAN [v2]
Volkan Yazici
Re: RFR: 8351339: WebSocket::sendBinary assume that user supplied buffers are BIG_ENDIAN [v2]
Daniel Fuchs
Re: RFR: 8351339: WebSocket::sendBinary assume that user supplied buffers are BIG_ENDIAN [v2]
Mark Sheppard
Re: RFR: 8351339: WebSocket::sendBinary assume that user supplied buffers are BIG_ENDIAN [v2]
Volkan Yazici
Re: RFR: 8351339: WebSocket::sendBinary assume that user supplied buffers are BIG_ENDIAN [v2]
Mark Sheppard
Re: RFR: 8351339: WebSocket::sendBinary assume that user supplied buffers are BIG_ENDIAN [v2]
Robert Engels
Re: RFR: 8351339: WebSocket::sendBinary assume that user supplied buffers are BIG_ENDIAN [v2]
Bernd
Re: RFR: 8351339: WebSocket::sendBinary assume that user supplied buffers are BIG_ENDIAN [v2]
Robert Engels
Re: RFR: 8351339: WebSocket::sendBinary assume that user supplied buffers are BIG_ENDIAN [v2]
Daniel Fuchs
Re: RFR: 8351339: WebSocket::sendBinary assume that user supplied buffers are BIG_ENDIAN [v3]
Volkan Yazici
Re: RFR: 8351339: WebSocket::sendBinary assume that user supplied buffers are BIG_ENDIAN [v3]
Mark Sheppard
Re: RFR: 8351339: WebSocket::sendBinary assume that user supplied buffers are BIG_ENDIAN [v3]
Robert Engels
Re: RFR: 8351339: WebSocket::sendBinary assume that user supplied buffers are BIG_ENDIAN [v3]
Volkan Yazici
Re: RFR: 8351339: WebSocket::sendBinary assume that user supplied buffers are BIG_ENDIAN [v3]
Mark Sheppard
Re: RFR: 8351339: WebSocket::sendBinary assume that user supplied buffers are BIG_ENDIAN [v4]
Volkan Yazici
Re: RFR: 8351339: WebSocket::sendBinary assume that user supplied buffers are BIG_ENDIAN [v4]
beppo-sturmtief
Re: RFR: 8351339: WebSocket::sendBinary assume that user supplied buffers are BIG_ENDIAN [v4]
Daniel Fuchs
Re: RFR: 8351339: WebSocket::sendBinary assume that user supplied buffers are BIG_ENDIAN [v4]
Michael McMahon
Re: RFR: 8351339: WebSocket::sendBinary assume that user supplied buffers are BIG_ENDIAN [v4]
Volkan Yazici
Re: RFR: 8351339: WebSocket::sendBinary assume that user supplied buffers are BIG_ENDIAN [v4]
Michael McMahon
Re: RFR: 8351339: WebSocket::sendBinary assume that user supplied buffers are BIG_ENDIAN [v4]
Volkan Yazici
Re: RFR: 8351339: WebSocket::sendBinary assume that user supplied buffers are BIG_ENDIAN [v4]
Michael McMahon
Re: RFR: 8351339: WebSocket::sendBinary assume that user supplied buffers are BIG_ENDIAN [v4]
Volkan Yazici
Re: RFR: 8351339: WebSocket::sendBinary assume that user supplied buffers are BIG_ENDIAN [v5]
Volkan Yazici
Re: RFR: 8351339: WebSocket::sendBinary assume that user supplied buffers are BIG_ENDIAN [v5]
Michael McMahon
Re: RFR: 8351339: WebSocket::sendBinary assume that user supplied buffers are BIG_ENDIAN [v5]
Daniel Fuchs
Re: RFR: 8351339: WebSocket::sendBinary assume that user supplied buffers are BIG_ENDIAN [v5]
Chen Liang
Re: RFR: 8351339: WebSocket::sendBinary assume that user supplied buffers are BIG_ENDIAN [v5]
Chen Liang
Re: RFR: 8351339: WebSocket::sendBinary assume that user supplied buffers are BIG_ENDIAN [v5]
Volkan Yazici
Re: RFR: 8351339: WebSocket::sendBinary assume that user supplied buffers are BIG_ENDIAN [v5]
Chen Liang
Re: RFR: 8351339: WebSocket::sendBinary assume that user supplied buffers are BIG_ENDIAN [v5]
Volkan Yazici
Re: RFR: 8351339: WebSocket::sendBinary assume that user supplied buffers are BIG_ENDIAN [v5]
Chen Liang
Re: RFR: 8351339: WebSocket::sendBinary assume that user supplied buffers are BIG_ENDIAN [v5]
Volkan Yazici
Re: RFR: 8351339: WebSocket::sendBinary assume that user supplied buffers are BIG_ENDIAN [v6]
Volkan Yazici
Re: RFR: 8351339: WebSocket::sendBinary assume that user supplied buffers are BIG_ENDIAN [v6]
Daniel Fuchs
Re: RFR: 8351339: WebSocket::sendBinary assume that user supplied buffers are BIG_ENDIAN [v7]
Volkan Yazici
Re: RFR: 8351339: WebSocket::sendBinary assume that user supplied buffers are BIG_ENDIAN [v7]
Chen Liang
Re: RFR: 8351339: WebSocket::sendBinary assume that user supplied buffers are BIG_ENDIAN [v7]
Mark Sheppard
Re: RFR: 8351339: WebSocket::sendBinary assume that user supplied buffers are BIG_ENDIAN [v7]
Michael McMahon
Re: RFR: 8351339: WebSocket::sendBinary assume that user supplied buffers are BIG_ENDIAN [v7]
Volkan Yazici
Re: RFR: 8351339: WebSocket::sendBinary assume that user supplied buffers are BIG_ENDIAN [v8]
Volkan Yazici
Re: RFR: 8351339: WebSocket::sendBinary assume that user supplied buffers are BIG_ENDIAN [v8]
Michael McMahon
Integrated: 8351339: WebSocket::sendBinary assume that user supplied buffers are BIG_ENDIAN
Volkan Yazici
RFR: 8351897: Extra closing curly brace typos in Javadoc
Archie Cobbs
Re: RFR: 8351897: Extra closing curly brace typos in Javadoc
Iris Clark
Re: RFR: 8351897: Extra closing curly brace typos in Javadoc
Archie Cobbs
Re: RFR: 8351897: Extra closing curly brace typos in Javadoc
Chen Liang
Re: RFR: 8351897: Extra closing curly brace typos in Javadoc [v2]
Archie Cobbs
Re: RFR: 8351897: Extra closing curly brace typos in Javadoc
Naoto Sato
Re: RFR: 8351897: Extra closing curly brace typos in Javadoc
Daniel Fuchs
Re: RFR: 8351897: Extra closing curly brace typos in Javadoc [v3]
Archie Cobbs
Re: RFR: 8351897: Extra closing curly brace typos in Javadoc [v3]
Chen Liang
Re: RFR: 8351897: Extra closing curly brace typos in Javadoc [v3]
Archie Cobbs
Re: RFR: 8351897: Extra closing curly brace typos in Javadoc [v2]
Archie Cobbs
Integrated: 8351897: Extra closing curly brace typos in Javadoc
Archie Cobbs
RFR: 8351419: java.net.http: Cleanup links in HttpResponse and module-info API doc comments
Daniel Fuchs
Re: RFR: 8351419: java.net.http: Cleanup links in HttpResponse and module-info API doc comments
Michael McMahon
Re: RFR: 8351419: java.net.http: Cleanup links in HttpResponse and module-info API doc comments [v2]
Daniel Fuchs
Earlier messages
Later messages