Klaus
I've created an RFE at https://bugs.openjdk.java.net/browse/JDK-8209137
to track this. I imagine the simplest solution would be to be able to
specify the local
address when constructing a HttpClient, and then all connections created
using that
client would be bound to the chosen address.
Hi,
I just discussed with a colleague that we dreadfully miss the ability in the old
HttpURLConnection to set the address to which the client locally binds, which we
require to get through the firewalls of our business partners when connecting
from a multihomed system. This repeatedly cause
Hi Nezih,
The client’s version is a default preferred version for requests that do not
specify an explicit version. As such, it does not prevent requests, attempting
to negotiate HTTP/2, from being sent, just that it is not the default. Given
that, then the priority value is still be applicable
Chris,
that's good to hear, I'll try it out.
Best,
Albert
On 07.08.2018 18:53, Chris Hegarty wrote:
Albert,
I haven’t yet looked at what happens in JDK 10, but just to say, since things
have moved on a lot in JDK 11 EA, that the same test runs with a reasonable
amount of memory and CPU with
The updated webrev looks fine to me, Chris.
Thanks,
Michael
On 07/08/2018, 10:52, Chris Hegarty wrote:
On 4 Aug 2018, at 14:08, Jaikiran Pai wrote:
...
Do you think this can be reworded a bit? Although I understand what's
being said here, the wording doesn't seem right. Maybe something like:
