On Fri, Dec 29, 2017 at 11:15 AM, Chris Hegarty
wrote:
> On 29 Dec 2017, at 00:33, Steven Schlansker
> wrote:
>> Thanks for the discussion!
>>
>> So, it sounds like amending the message by default is going to be a
>> non-starter -- but at least adding the information otherwise might be
>> poss
Hello,
Yes. i think OpenJDK has only a Socks Implementation, but it is a general
problem that there is no API framework to communicate network problems with
intermediates.
Gruss
Bernd
--
http://bernd.eckenfels.net
From: Chris Hegarty
Sent: Wednesday, January 3,
Hi Bernd,
Are you specifically talking about a SOCKS proxy, or something else?
-Chris.
> On 3 Jan 2018, at 12:10, Bernd Eckenfels wrote:
>
> Hello,
>
> Just to add to the discussion, if proxies are used, the error should make
> clear if the problem is connecting the proxy or the endpoint. An
Hello,
Just to add to the discussion, if proxies are used, the error should make clear
if the problem is connecting the proxy or the endpoint. And for that case
(especially with multiple proxies) the actual failed address is also
interesting for trouble shooting (in that case higher level code
On 02/01/2018 21:25, Steven Schlansker wrote:
:
This would definitely be better than nothing! But it's still difficult, for
example a common allocation pattern for us would be to assign networks to
availability zones:
10.0.1.0/24 10.0.2.0/24 10.0.3.0/24
then if you pick the same last number
