On Mon, 17 May 2021 18:23:41 GMT, Weijun Wang wrote:
> Please review this implementation of [JEP
> 411](https://openjdk.java.net/jeps/411).
>
> The code change is divided into 3 commits. Please review them one by one.
>
> 1.
> https://github.com/openjdk/jdk/commit/576161d15423f58281e384174d28
On Mon, 17 May 2021 17:51:36 GMT, Weijun Wang wrote:
> Please review the test changes for [JEP
> 411](https://openjdk.java.net/jeps/411).
>
> With JEP 411 and the default value of `-Djava.security.manager` becoming
> `disallow`, tests calling `System.setSecurityManager()` need
> `-Djava.secu
On Mon, 17 May 2021 17:51:36 GMT, Weijun Wang wrote:
> Please review the test changes for [JEP
> 411](https://openjdk.java.net/jeps/411).
>
> With JEP 411 and the default value of `-Djava.security.manager` becoming
> `disallow`, tests calling `System.setSecurityManager()` need
> `-Djava.secu
On Mon, 17 May 2021 18:23:41 GMT, Weijun Wang wrote:
> Please review this implementation of [JEP
> 411](https://openjdk.java.net/jeps/411).
>
> The code change is divided into 3 commits. Please review them one by one.
>
> 1.
> https://github.com/openjdk/jdk/commit/576161d15423f58281e384174d28
On Mon, 17 May 2021 18:23:41 GMT, Weijun Wang wrote:
> Please review this implementation of [JEP
> 411](https://openjdk.java.net/jeps/411).
>
> The code change is divided into 3 commits. Please review them one by one.
>
> 1.
> https://github.com/openjdk/jdk/commit/576161d15423f58281e384174d28
Please review this implementation of [JEP
411](https://openjdk.java.net/jeps/411).
The code change is divided into 3 commits. Please review them one by one.
1.
https://github.com/openjdk/jdk/commit/576161d15423f58281e384174d28c9f9be7941a1
The essential change for this JEP, including the `@Depr
Please review the test changes for [JEP 411](https://openjdk.java.net/jeps/411).
With JEP 411 and the default value of `-Djava.security.manager` becoming
`disallow`, tests calling `System.setSecurityManager()` need
`-Djava.security.manager=allow` when launched. This PR covers such changes for
Hi,
I think Firefox Developer Tools should not display the TE request header
value as "Trailers" since this is not a valid value as per the
specification, and it is actually sending "trailers" over the wire [1].
I have submitted a bug regarding this [2].
[1] :
https://hg.mozilla.org/mozilla-cent
On Mon, 17 May 2021 09:53:06 GMT, Julia Boes wrote:
> The tests for `afterHandler` filters expect the filter operation to happen
> before the assertion. Very rarely this is not the case, the calling thread
> reads the response before the filter operation is executed, so the test value
> is not
On Mon, 17 May 2021 09:53:06 GMT, Julia Boes wrote:
> The tests for `afterHandler` filters expect the filter operation to happen
> before the assertion. Very rarely this is not the case, the calling thread
> reads the response before the filter operation is executed, so the test value
> is not
The tests for `afterHandler` filters expect the filter operation to happen
before the assertion. Very rarely this is not the case, the calling thread
reads the response before the filter operation is executed, so the test value
is not set before it is asserted.
This fix uses a `CompletableFutur
11 matches
Mail list logo