On Sun, 15 May 2022 06:43:27 GMT, Jaikiran Pai wrote:
>> This change proposes to implement the enhancement noted in
>> https://bugs.openjdk.java.net/browse/JDK-8209137.
>>
>> The change introduces a new API to allow applications to build a
>> `java.net.http.HTTPClient` configured with a specif
On Sat, 7 May 2022 11:46:37 GMT, Daniel Fuchs wrote:
>> Hi, please find here a patch that solves a rare intermittent test failure
>> observed in the test `java/net/httpclient/ExecutorShutdown.java`
>>
>> A race condition coupled with some too eager synchronization was causing a
>> deadlock bet
On Sat, 7 May 2022 11:46:37 GMT, Daniel Fuchs wrote:
>> Hi, please find here a patch that solves a rare intermittent test failure
>> observed in the test `java/net/httpclient/ExecutorShutdown.java`
>>
>> A race condition coupled with some too eager synchronization was causing a
>> deadlock bet
On Thu, 12 May 2022 10:51:04 GMT, Daniel Fuchs wrote:
>> In relation to
>> [JDK-8244681](https://bugs.openjdk.java.net/browse/JDK-8244681), please find
>> here a patch that addresses possibly lossy conversions in java.net.http
>
> Daniel Fuchs has updated the pull request incrementally with one
On Wed, 11 May 2022 17:10:45 GMT, Daniel Fuchs wrote:
>> src/java.net.http/share/classes/jdk/internal/net/http/hpack/QuickHuffman.java
>> line 739:
>>
>>> 737: buffer |= (codeValueOf(c) >>> bufferLen); //
>>> append
>>> 738: bufferLen += (int) le
On Wed, 11 May 2022 15:42:25 GMT, Daniel Fuchs wrote:
> In relation to
> [JDK-8244681](https://bugs.openjdk.java.net/browse/JDK-8244681), please find
> here a patch that addresses possibly lossy conversions in java.net.http
src/java.net.http/share/classes/jdk/internal/net/http/hpack/QuickHuffm
On Wed, 11 May 2022 08:54:48 GMT, Jaikiran Pai wrote:
>> src/java.net.http/share/classes/java/net/http/HttpClient.java line 378:
>>
>>> 376: *
>>> 377: * @implSpec The default implementation of this method throws
>>> 378: * {@code UnsupportedOperationException}. {@code
On Tue, 10 May 2022 13:51:37 GMT, Jaikiran Pai wrote:
>> This change proposes to implement the enhancement noted in
>> https://bugs.openjdk.java.net/browse/JDK-8209137.
>>
>> The change introduces a new API to allow applications to build a
>> `java.net.http.HTTPClient` configured with a specif
On Mon, 9 May 2022 12:37:59 GMT, Daniel Fuchs wrote:
>> Hi,
>>
>> Please find here a simple test fix that re-architecture ShortResponseBody
>> for better resource usage.
>> The test is split to test GET and POST separately and avoids testing GET
>> twice.
>
> Daniel Fuchs has updated the pull
On Sat, 7 May 2022 11:46:32 GMT, Daniel Fuchs wrote:
>> Hi,
>>
>> Please find here a simple test fix that re-architecture ShortResponseBody
>> for better resource usage.
>> The test is split to test GET and POST separately and avoids testing GET
>> twice.
>
> Daniel Fuchs has updated the pull
On Thu, 5 May 2022 12:55:57 GMT, Michael Felt wrote:
>> with IP "0.0.0.0"
>>
>> - it either does nothing and ping fails, or, in some virtual environments
>> is treated as the default route address.
>> - IPv6 support for ::1 is available since 1977; however, ::0 is not accepted
>> as a vaild psue
On Sat, 30 Apr 2022 09:55:16 GMT, Michael Felt wrote:
>> with IP "0.0.0.0"
>>
>> - it either does nothing and ping fails, or, in some virtual environments
>> is treated as the default route address.
>> - IPv6 support for ::1 is available since 1977; however, ::0 is not accepted
>> as a vaild psu
On Wed, 27 Apr 2022 15:27:45 GMT, Michael Felt wrote:
>> with IP "0.0.0.0"
>>
>> - it either does nothing and ping fails, or, in some virtual environments
>> is treated as the default route address.
>> - IPv6 support for ::1 is available since 1977; however, ::0 is not accepted
>> as a vaild psu
On Wed, 27 Apr 2022 09:43:52 GMT, Michael McMahon wrote:
> Hi,
>
> Can I get the following fix reviewed please? JDK-8284890 was pushed yesterday
> and is causing failures on older versions of macOS that do not support the
> option. The fix here is to check at initialization tim
On Wed, 27 Apr 2022 14:12:40 GMT, Daniel Fuchs wrote:
>> Michael McMahon has updated the pull request incrementally with one
>> additional commit since the last revision:
>>
>> updated test
>
> test/jdk/jdk/net/ExtendedSocketOption/DontFragmentTest.java line 44
list of supported options. The error causes
> the new test and two existing ones to fail. I will remove the two tests from
> the problem list separately.
>
> Thanks,
> Michael.
Michael McMahon has updated the pull request incrementally with one additional
commit since
On Wed, 27 Apr 2022 14:10:55 GMT, Daniel Fuchs wrote:
>> Michael McMahon has updated the pull request incrementally with one
>> additional commit since the last revision:
>>
>> updated test
>
> src/jdk.net/macosx/native/libextnet/MacOSXSocketOptions.c line
list of supported options. The error causes
> the new test and two existing ones to fail. I will remove the two tests from
> the problem list separately.
>
> Thanks,
> Michael.
Michael McMahon has updated the pull request incrementally with one additional
commit since t
On Wed, 27 Apr 2022 11:02:08 GMT, Daniel Fuchs wrote:
>> Hi,
>>
>> Can I get the following fix reviewed please? JDK-8284890 was pushed
>> yesterday and is causing failures on older versions of macOS that do not
>> support the option. The fix here is to check at initialization time whether
>>
On Wed, 27 Apr 2022 09:43:52 GMT, Michael McMahon wrote:
> Hi,
>
> Can I get the following fix reviewed please? JDK-8284890 was pushed yesterday
> and is causing failures on older versions of macOS that do not support the
> option. The fix here is to check at initialization tim
On Wed, 27 Apr 2022 09:43:52 GMT, Michael McMahon wrote:
> Hi,
>
> Can I get the following fix reviewed please? JDK-8284890 was pushed yesterday
> and is causing failures on older versions of macOS that do not support the
> option. The fix here is to check at initialization tim
Hi,
Can I get the following fix reviewed please? JDK-8284890 was pushed yesterday
and is causing failures on older versions of macOS that do not support the
option. The fix here is to check at initialization time whether it is supported
before adding it to the list of supported options. The err
On Tue, 26 Apr 2022 16:41:08 GMT, Michael McMahon wrote:
> Hi,
>
> Could I get the following small test update reviewed please?
> It includes a test scenario that should have been included with JDK-8284890
>
> Thanks,
> Michael
This pull request has been closed wit
On Tue, 26 Apr 2022 16:41:08 GMT, Michael McMahon wrote:
> Hi,
>
> Could I get the following small test update reviewed please?
> It includes a test scenario that should have been included with JDK-8284890
>
> Thanks,
> Michael
I'm closing this PR as the rela
Hi,
Could I get the following small test update reviewed please?
It includes a test scenario that should have been included with JDK-8284890
Thanks,
Michael
-
Commit messages:
- test update
Changes: https://git.openjdk.java.net/jdk/pull/8405/files
Webrev: https://webrevs.openjdk.
On Thu, 14 Apr 2022 16:04:22 GMT, Michael McMahon wrote:
> Hi,
>
> Could I get the following PR review please? It adds a new JDK specific
> extended socket option
> called IP_DONTFRAGMENT, which disables IP packet fragmentation in both IPv4
> and IPv6
> UDP sockets (NIO D
> (Dont Fragment) bit
> in the IP header. There is no equivalent in the IPv6 packet header as
> fragmentation is implemented
> exclusively by the sending and receiving nodes.
>
> Thanks,
> Michael
Michael McMahon has updated the pull request incrementally with one additiona
On Sat, 16 Apr 2022 11:06:21 GMT, Daniel Fuchs wrote:
>> These changes make sure that pending requests are terminated if the selector
>> manager thread exits due to exceptions.
>> This includes:
>>1. completing CompletableFutures that were returned to the caller code
>>2. cancelling requ
Hi,
https://bugs.openjdk.java.net/browse/JDK-8285240
contains the release note for the TLS Channel binding enhancement in JDK
19 added in:
https://bugs.openjdk.java.net/browse/JDK-8279842
(PR: https://github.com/openjdk/jdk/pull/7065)
The release note uses the explanatory text from the CSR
> (Dont Fragment) bit
> in the IP header. There is no equivalent in the IPv6 packet header as
> fragmentation is implemented
> exclusively by the sending and receiving nodes.
>
> Thanks,
> Michael
Michael McMahon has updated the pull request incrementally with one additiona
On Tue, 19 Apr 2022 16:07:29 GMT, Daniel Fuchs wrote:
>> I'm not sure there is value in testing all of these permutations.
>> Distinguishing DatagramChannel and DatagramSocket probably made sense, but
>> it's all the same implementation under the hood.
>
> 1. `DatagramChannel.open()` => opens a
> (Dont Fragment) bit
> in the IP header. There is no equivalent in the IPv6 packet header as
> fragmentation is implemented
> exclusively by the sending and receiving nodes.
>
> Thanks,
> Michael
Michael McMahon has updated the pull request incrementally with one additional
On Tue, 19 Apr 2022 14:50:57 GMT, Daniel Fuchs wrote:
>> Michael McMahon has updated the pull request incrementally with one
>> additional commit since the last revision:
>>
>> fix whitespace
>
> src/jdk.net/windows/native/libextnet/WindowsSocke
> (Dont Fragment) bit
> in the IP header. There is no equivalent in the IPv6 packet header as
> fragmentation is implemented
> exclusively by the sending and receiving nodes.
>
> Thanks,
> Michael
Michael McMahon has updated the pull request incrementally with one addition
> (Dont Fragment) bit
> in the IP header. There is no equivalent in the IPv6 packet header as
> fragmentation is implemented
> exclusively by the sending and receiving nodes.
>
> Thanks,
> Michael
Michael McMahon has updated the pull request incrementally with one additional
> (Dont Fragment) bit
> in the IP header. There is no equivalent in the IPv6 packet header as
> fragmentation is implemented
> exclusively by the sending and receiving nodes.
>
> Thanks,
> Michael
Michael McMahon has updated the pull request with a new target base due to a
On Fri, 15 Apr 2022 10:04:48 GMT, Daniel Jeliński wrote:
>> Michael McMahon has updated the pull request incrementally with one
>> additional commit since the last revision:
>>
>> builds in github action now
>
> src/jdk.net/windows/native/libextnet/WindowsSoc
> (Dont Fragment) bit
> in the IP header. There is no equivalent in the IPv6 packet header as
> fragmentation is implemented
> exclusively by the sending and receiving nodes.
>
> Thanks,
> Michael
Michael McMahon has updated the pull request incrementally with one additional
On Fri, 15 Apr 2022 09:19:48 GMT, Daniel Fuchs wrote:
>> Hi,
>>
>> Could I get the following PR review please? It adds a new JDK specific
>> extended socket option
>> called IP_DONTFRAGMENT, which disables IP packet fragmentation in both IPv4
>> and IPv6
>> UDP sockets (NIO DatagramChannels).
Hi,
Could I get the following PR review please? It adds a new JDK specific extended
socket option
called IP_DONTFRAGMENT, which disables IP packet fragmentation in both IPv4 and
IPv6
UDP sockets (NIO DatagramChannels). For IPv4 in particular, it sets the DF
(Dont Fragment) bit
in the IP header.
On Thu, 14 Apr 2022 18:45:10 GMT, Daniel Fuchs wrote:
>> java/net/httpclient/http2/TLSConnection.java has been observed failing (even
>> though rarely) in test jobs.
>>
>> The issue is that the handler used on the the server sides maintains a
>> volatile `sslSession` field which it sets when r
On Thu, 10 Mar 2022 11:17:26 GMT, Daniel Fuchs wrote:
>> These changes make sure that pending requests are terminated if the selector
>> manager thread exits due to exceptions.
>> This includes:
>>1. completing CompletableFutures that were returned to the caller code
>>2. cancelling requ
On Tue, 29 Mar 2022 19:43:50 GMT, Daniel Fuchs wrote:
>> src/java.net.http/share/classes/jdk/internal/net/http/Http1Request.java line
>> 302:
>>
>>> 300:
>>> 301: // GET with no body should not set the Content-Length header
>>> 302: if (requestPublisher != null ||
>>> !"GET".e
On Fri, 4 Mar 2022 09:37:21 GMT, Michael McMahon wrote:
> Hi,
>
> Could I get the following change reviewed please, which is to disable the MD5
> message digest algorithm by default in the HTTP Digest authentication
> mechanism? The algorithm can be opted into by setting a new
s" to include the value MD5. The change also
> updates the Digest authentication implementation to use some of the more
> secure features defined in RFC7616, such as username hashing and additional
> digest algorithms like SHA256 and SHA512-256.
>
> - Michael
Michael McMa
On Mon, 28 Mar 2022 09:29:58 GMT, Daniel Fuchs wrote:
>> No, the digest field refers to the actual message digest algorithm (as known
>> to the security libraries). The algorithm field holds the algorithm name as
>> it is defined in RFC7616.
>
> I am confused here - because you converted `algo
On Fri, 25 Mar 2022 17:21:11 GMT, Daniel Fuchs wrote:
>> Michael McMahon has updated the pull request incrementally with one
>> additional commit since the last revision:
>>
>> forgot update to DigestAuth test
>
> src/java.base/share/cla
On Fri, 25 Mar 2022 15:07:40 GMT, Michael McMahon wrote:
>> Hi,
>>
>> Could I get the following change reviewed please, which is to disable the
>> MD5 message digest algorithm by default in the HTTP Digest authentication
>> mechanism? The algorithm can be opte
s" to include the value MD5. The change also
> updates the Digest authentication implementation to use some of the more
> secure features defined in RFC7616, such as username hashing and additional
> digest algorithms like SHA256 and SHA512-256.
>
> - Michael
Michael McMahon
s" to include the value MD5. The change also
> updates the Digest authentication implementation to use some of the more
> secure features defined in RFC7616, such as username hashing and additional
> digest algorithms like SHA256 and SHA512-256.
>
> - Michael
Michael McMa
s" to include the value MD5. The change also
> updates the Digest authentication implementation to use some of the more
> secure features defined in RFC7616, such as username hashing and additional
> digest algorithms like SHA256 and SHA512-256.
>
> - Michael
Michael McMahon
On Mon, 14 Mar 2022 16:45:24 GMT, Aleksei Efimov wrote:
>> The following fix seals the `java.net.InetAddress` class and permits only
>> two implementations - `java.net.Inet4Address` and `java.net.Inet6Address`.
>>
>> No issues have been detected by regression and JCK tests.
>>
>> Links: [JBS]
On Fri, 11 Mar 2022 18:12:27 GMT, Daniel Fuchs wrote:
>> Michael McMahon has updated the pull request incrementally with one
>> additional commit since the last revision:
>>
>> update after second review round
>
> src/java.base/share/cla
On Mon, 14 Mar 2022 13:21:21 GMT, Daniel Fuchs wrote:
>> src/java.net.http/share/classes/jdk/internal/net/http/Http2ClientImpl.java
>> line 155:
>>
>>> 153: boolean offerConnection(Http2Connection c) {
>>> 154: if (debug.on()) debug.log("offering to the connection pool:
>>> %s", c)
On Thu, 10 Mar 2022 17:05:32 GMT, Daniel Fuchs wrote:
>> Please find enclosed a patch that solves an intermittent issue detected by
>> the CancelRequestTest.java
>>
>> If during an HTTP upgrade from HTTP/1.1 to HTTP/2, the request is cancelled
>> after the Http2Connection has been created, and
s" to include the value MD5. The change also
> updates the Digest authentication implementation to use some of the more
> secure features defined in RFC7616, such as username hashing and additional
> digest algorithms like SHA256 and SHA512-256.
>
> - Michael
Michael McMa
s" to include the value MD5. The change also
> updates the Digest authentication implementation to use some of the more
> secure features defined in RFC7616, such as username hashing and additional
> digest algorithms like SHA256 and SHA512-256.
>
> - Michael
Michael McMahon
On Thu, 10 Mar 2022 17:05:32 GMT, Daniel Fuchs wrote:
>> Please find enclosed a patch that solves an intermittent issue detected by
>> the CancelRequestTest.java
>>
>> If during an HTTP upgrade from HTTP/1.1 to HTTP/2, the request is cancelled
>> after the Http2Connection has been created, and
On Fri, 11 Mar 2022 17:37:44 GMT, Michael McMahon wrote:
>> Hi,
>>
>> Could I get the following change reviewed please, which is to disable the
>> MD5 message digest algorithm by default in the HTTP Digest authentication
>> mechanism? The algorithm can be opte
s" to include the value MD5. The change also
> updates the Digest authentication implementation to use some of the more
> secure features defined in RFC7616, such as username hashing and additional
> digest algorithms like SHA256 and SHA512-256.
>
> - Michael
Michael McMahon
On Mon, 7 Mar 2022 14:41:47 GMT, Weijun Wang wrote:
>> 2nd test of https://datatracker.ietf.org/doc/html/rfc7616#section-3.9 is on
>> this algorithm, but it requires UTF-8 charset support and a way to provide a
>> predefined cnonce. If it's not worth modifying our implementation to create
>> a
On Thu, 10 Mar 2022 15:02:17 GMT, Weijun Wang wrote:
>> Michael McMahon has updated the pull request incrementally with two
>> additional commits since the last revision:
>>
>> - update
>> - update after first review round
>
> src/java.base/sha
On Thu, 10 Mar 2022 14:26:28 GMT, Weijun Wang wrote:
>> Michael McMahon has updated the pull request incrementally with two
>> additional commits since the last revision:
>>
>> - update
>> - update after first review round
>
> src/java.base/
On Thu, 10 Mar 2022 14:21:41 GMT, Weijun Wang wrote:
>> Michael McMahon has updated the pull request incrementally with two
>> additional commits since the last revision:
>>
>> - update
>> - update after first review round
>
> src/java.base/share/
On Wed, 9 Mar 2022 15:41:08 GMT, Weijun Wang wrote:
>> Michael McMahon has updated the pull request incrementally with two
>> additional commits since the last revision:
>>
>> - update
>> - update after first review round
>
> src/java.base/sha
On Wed, 9 Mar 2022 15:18:43 GMT, Daniel Fuchs wrote:
>> Michael McMahon has updated the pull request incrementally with two
>> additional commits since the last revision:
>>
>> - update
>> - update after first review round
>
> src/java.base/sha
On Wed, 9 Mar 2022 14:23:24 GMT, Weijun Wang wrote:
>> Michael McMahon has updated the pull request incrementally with two
>> additional commits since the last revision:
>>
>> - update
>> - update after first review round
>
> src/java.base/sha
On Wed, 9 Mar 2022 15:53:02 GMT, Daniel Fuchs wrote:
>> src/java.base/share/classes/sun/net/www/protocol/http/DigestAuthentication.java
>> line 85:
>>
>>> 83: public String run() {
>>> 84: return Security.getProperty(secPropName)
>>> 85:
On Mon, 7 Mar 2022 20:35:13 GMT, Sean Mullan wrote:
>> Michael McMahon has updated the pull request incrementally with two
>> additional commits since the last revision:
>>
>> - update
>> - update after first review round
>
> src/java.base/sha
s" to include the value MD5. The change also
> updates the Digest authentication implementation to use some of the more
> secure features defined in RFC7616, such as username hashing and additional
> digest algorithms like SHA256 and SHA512-256.
>
> - Michael
Michael McMahon
On Sat, 5 Mar 2022 15:07:15 GMT, Jaikiran Pai wrote:
>> Hi,
>>
>> Could I get the following change reviewed please, which is to disable the
>> MD5 message digest algorithm by default in the HTTP Digest authentication
>> mechanism? The algorithm can be opted into by setting a new system propert
I'm wrong. It is implemented in the security libs. So, that means we can
support it also
Michael
On 07/03/2022 12:24, Michael McMahon wrote:
Bernd,
In that case we should defer to the security libraries to implement
SHA-512-256, which does not seem to be supported currently. We al
://bernd.eckenfels.net
Von: net-dev im Auftrag von Michael
McMahon
Gesendet: Monday, March 7, 2022 12:04:02 PM
An:net-dev@openjdk.java.net
Betreff: Re: RFR: 8281561: Disable http DIGEST mechanism with MD5 by default
On Fri, 4 Mar 2022 14:59:48 GMT, Weijun Wang wrote:
Hi
On Fri, 4 Mar 2022 16:26:52 GMT, Weijun Wang wrote:
>> Hi,
>>
>> Could I get the following change reviewed please, which is to disable the
>> MD5 message digest algorithm by default in the HTTP Digest authentication
>> mechanism? The algorithm can be opted into by setting a new system property
On Fri, 4 Mar 2022 14:59:48 GMT, Weijun Wang wrote:
>> Hi,
>>
>> Could I get the following change reviewed please, which is to disable the
>> MD5 message digest algorithm by default in the HTTP Digest authentication
>> mechanism? The algorithm can be opted into by setting a new system property
echanisms so the update
won’t change the behavior? (If there is no negotiation?)
Gruss
Bernd
--
http://bernd.eckenfels.net
Von: net-dev im Auftrag von Michael
McMahon
Gesendet: Friday, March 4, 2022 1:33:06 PM
An:net-dev@openjdk.java.net
Betreff: Re: RFR: 8281561:
On Fri, 4 Mar 2022 14:39:50 GMT, Jaikiran Pai wrote:
>> Hi,
>>
>> Could I get the following change reviewed please, which is to disable the
>> MD5 message digest algorithm by default in the HTTP Digest authentication
>> mechanism? The algorithm can be opted into by setting a new system propert
On Fri, 4 Mar 2022 14:11:00 GMT, Jaikiran Pai wrote:
>> Hi,
>>
>> Could I get the following change reviewed please, which is to disable the
>> MD5 message digest algorithm by default in the HTTP Digest authentication
>> mechanism? The algorithm can be opted into by setting a new system propert
On Fri, 4 Mar 2022 13:13:47 GMT, Daniel Fuchs wrote:
>> Hi,
>>
>> Could I get the following change reviewed please, which is to disable the
>> MD5 message digest algorithm by default in the HTTP Digest authentication
>> mechanism? The algorithm can be opted into by setting a new system propert
On Fri, 4 Mar 2022 09:37:21 GMT, Michael McMahon wrote:
> Hi,
>
> Could I get the following change reviewed please, which is to disable the MD5
> message digest algorithm by default in the HTTP Digest authentication
> mechanism? The algorithm can be opted into by setting a new
On Fri, 4 Mar 2022 12:12:25 GMT, Daniel Fuchs wrote:
> > I considered that and implemented it that way at the start, but what you
> > would end up with then is users running their code with something like:
> > -DdisabledAlgNames=""
> > I find that style leads to a much less explicit "opting in"
On Fri, 4 Mar 2022 11:25:38 GMT, Daniel Fuchs wrote:
> Should we instead have a property to disable algorithms, whose default value
> would contain "MD5" by default?
I considered that and implemented it that way at the start, but what you would
end up with then is users running their code with
On Thu, 3 Mar 2022 16:13:37 GMT, Jaikiran Pai wrote:
> Can I please get a review of this change which proposes to fix the issue
> noted in https://bugs.openjdk.java.net/browse/JDK-8282617?
>
> The `HttpClient` class uses a `inCache` (internal) field to keep track of
> whether a connection is
Hi,
Could I get the following change reviewed please, which is to disable the MD5
message digest algorithm by default in the HTTP Digest authentication
mechanism? The algorithm can be opted into by setting a new system property
"http.auth.digest.enabledDigestAlgs" to include the value MD5. The
On Fri, 4 Mar 2022 09:37:21 GMT, Michael McMahon wrote:
> Hi,
>
> Could I get the following change reviewed please, which is to disable the MD5
> message digest algorithm by default in the HTTP Digest authentication
> mechanism? The algorithm can be opted into by setting a new
On Wed, 16 Feb 2022 21:27:40 GMT, Daniel Fuchs wrote:
> Please find here a changeset to ProblemList
> sun/net/www/protocol/https/HttpsURLConnection/B6216082.java until JDK-8282017
> is fixed
LGTM
-
Marked as reviewed by michaelm (Reviewer).
PR: https://git.openjdk.java.net/jdk/p
On Fri, 4 Feb 2022 13:11:02 GMT, Michael McMahon wrote:
> Hi,
>
> Could I get the following patch reviewed please? (A CSR is also required
> which I will submit when the docs are agreed)
>
> It adds a pair of new system properties to make the keep alive timer in
> java.
posed property names are:
>
> "http.keepAlive.time.server" and "http.keepAlive.time.proxy"
>
> Thanks,
> Michael
Michael McMahon has updated the pull request incrementally with one additional
commit since the last revision:
remove extraneous .swp file
-
C
posed property names are:
>
> "http.keepAlive.time.server" and "http.keepAlive.time.proxy"
>
> Thanks,
> Michael
Michael McMahon has updated the pull request incrementally with one additional
commit since the last revision:
tighten up spec wording and move props besid
posed property names are:
>
> "http.keepAlive.time.server" and "http.keepAlive.time.proxy"
>
> Thanks,
> Michael
Michael McMahon has updated the pull request incrementally with one additional
commit since the last revision:
Fixed test case problem and update f
On Mon, 14 Feb 2022 13:38:06 GMT, Daniel Fuchs wrote:
>> Michael McMahon has updated the pull request with a new target base due to a
>> merge or a rebase. The incremental webrev excludes the unrelated changes
>> brought in by the merge/rebase. The pull request cont
posed property names are:
>
> "http.keepAlive.time.server" and "http.keepAlive.time.proxy"
>
> Thanks,
> Michael
Michael McMahon has updated the pull request with a new target base due to a
merge or a rebase. The incremental webrev excludes the unrelated changes
b
posed property names are:
>
> "http.keepAlive.time.server" and "http.keepAlive.time.proxy"
>
> Thanks,
> Michael
Michael McMahon has updated the pull request with a new target base due to a
merge or a rebase. The incremental webrev excludes the unrelated changes
b
On Fri, 4 Feb 2022 14:11:49 GMT, Daniel Fuchs wrote:
>> Hi,
>>
>> Could I get the following patch reviewed please? (A CSR is also required
>> which I will submit when the docs are agreed)
>>
>> It adds a pair of new system properties to make the keep alive timer in
>> java.net.HttpURLConnecti
Hi,
Could I get the following patch reviewed please? (A CSR is also required which
I will submit when the docs are agreed)
It adds a pair of new system properties to make the keep alive timer in
java.net.HttpURLConnection configurable.
The proposed property names are:
"http.keepAlive.time.serv
On Thu, 3 Feb 2022 09:24:46 GMT, Julia Boes wrote:
> This change updates the tests in question to handle the case where sym link
> creation is not supported, as observed on Windows 11 where additional
> privileges are required to create sym links.
>
> Testing: tier 1-3 across platforms, plus t
On Fri, 28 Jan 2022 09:45:02 GMT, Daniel Fuchs wrote:
> Please find enclosed a simple test fix for:
> 8280868: LineBodyHandlerTest.java creates and discards too many clients
>
> The LineBodyHandlerTest.java creates and discards many clients (64).
> The test has been observed failing intermittent
On Thu, 13 Jan 2022 12:10:11 GMT, Michael McMahon wrote:
> Hi,
>
> This change adds Channel Binding Token (CBT) support to HTTPS
> (java.net.HttpsURLConnection) when used with the Negotiate (SPNEGO, Kerberos)
> authentication scheme. When enabled, the implementation preemptivel
;, "b.c" and all hosts under the domain "d.com" and all of its
> sub-domains.
>
> A test will be added separately to the implementation.
>
> Bug report: https://bugs.openjdk.java.net/browse/JDK-8279842
>
> Thanks,
> Michael
Michael McMahon has
On Fri, 28 Jan 2022 14:46:32 GMT, Michael Felt wrote:
>> If it defeats the purpose, then it needs to be skipped.
>>
>> * When I was trying to understand the test, it seemed to be that it
>> _assumed_ that "0.0.0.0" was 'converted' to 127.0.0.1.
>> * If there is an international standard (ISO, P
1 - 100 of 1001 matches
Mail list logo
