On Tue, Mar 28, 2017 at 12:26:22PM +0100, ashtonho...@ymail.com wrote:
> Hi all
>
> I was looking through the archives but did not find any answers to these
> questions so I figured I'd try here, hopefully this helps someone else as
> well.
>
> I've done some testing on the httpserver and come
On Thu, Aug 04, 2016 at 10:15:38AM +, Langer, Christoph wrote:
> To sum it up: The only added value of NET_ThrowByNameWithLastError is that
> there could be cases where you might see an error number value - though I
> think this is very unlikely to happen. But if you say this is valuable I
>
osoft.
Matthew.
--
Sent from my mobile device.
On March 22, 2014 8:30:28 AM PDT, chris...@zoulas.com wrote:
>On Mar 21, 11:48pm, mh...@mhcomputing.net (Matthew Hall) wrote:
>-- Subject: Re: Review Request of JDK Enhancement Proposal: DTLS
>
>| The following bug and source code
-- Subject: Re: Review Request of JDK Enhancement Proposal: DTLS
>
> | Networking experts, any suggestion?
>
> I have not seen pmtu exposed at the application layer before. Has anyone
> else?
>
> christos
>
> |
> | Xuelei
> |
> | On 3/21/2014 8:28 AM, Matthew Ha
On Thu, Aug 15, 2013 at 10:08:35AM -0700, Mike Duigou wrote:
> I've been confused through this discussion as to why a trailing dot would be
> regarded as illegal.
>
> Historically a trailing dot has been frequently (though not universally) used
> to denote a fully qualified domain name.
>
> htt
But, DNS considers "." as the valid root zone...
--
Sent from my mobile device.
Xuelei Fan wrote:
>On 8/9/2013 10:14 AM, Weijun Wang wrote:
>>
>>
>> On 8/9/13 9:37 AM, Xuelei Fan wrote:
>>> On 8/9/2013 9:22 AM, Weijun Wang wrote:
I tried nslookup. Those with ".." inside are illegal,
On Tue, Aug 06, 2013 at 06:18:39PM +0100, Michael McMahon wrote:
> Documenting in release notes is okay too, but I suspect developers are not
> likely to look there at first anyway. Thinking aloud, it would be nice if
> some kind of annotation could be associated with the affected constructors
>
Take a look here for more clarity:
http://en.wikipedia.org/wiki/Fully_qualified_domain_name
--
Sent from my mobile device.
Matthew Hall wrote:
>Trailing dots are allowed in plain DNS (thus almost surely in IDN), and
>the single dot represents the root zone. So you have to be careful
&
Trailing dots are allowed in plain DNS (thus almost surely in IDN), and the
single dot represents the root zone. So you have to be careful making this sort
of change to check the DNS RFCs first.
Matthew.
--
Sent from my mobile device.
Weijun Wang wrote:
>I am not sure if IDN.java is the corre
On Thu, Aug 01, 2013 at 02:18:01PM -0700, Stuart Marks wrote:
> This isn't definitive, of course, but it does seem to supply some
> evidence that making this change would result in a relatively minor
> source incompatibility.
Good, maybe it will allow a true fix to be made in this case.
Matthew.
On Wed, Jul 31, 2013 at 02:38:26PM -0700, Stuart Marks wrote:
> The alternative is to add "@throws SocketException never" to the
> javadoc, just to get rid of the doclint warning, but this has the
> consequence of requiring people to keep dead code around
> indefinitely, and furthermore it requires
On Wed, Jul 17, 2013 at 03:45:19PM -0400, roger riggs wrote:
> Hi,
>
> Is there support in SSLEngine/TLS to support Pre-Shared Keys?
> I have been looking for relevant doc and have not stumbled upon it.
>
> Thanks, Roger
No, there isn't any support for PSK Ciphers yet, although some of the
cons
I don't think the OS X JDK is open to the community yet but I could be wrong.
You can try increasing the amount of mbuf clusters (nmbclusters) in the sysctl
and rebooting to see if it helps, this is what I did. But even that didn't fix
all my issues with their brokenness in their network stack.
I ran into a similar issue before on OS X... there are some bugs Apple
introduced into their BSD kernel, where they limited the amount of buffer space
you could get for a single socket to a certain percentage of the global mbuf
and skbuff pool, in a brain damaged way which causes more problems t
On Thu, Jun 13, 2013 at 12:11:34AM +0200, Bernd Eckenfels wrote:
> dns(only)-based providers are not the best option for general
> purpose resolving because (besides the fact that they will not use
> alternative naming methods which are typically used (mDNS, WINS,
> Hostsfile)) they also cannot use
On Wed, Jun 12, 2013 at 11:05:00PM +0200, Bernd Eckenfels wrote:
> If you think it is not a good idea to fix this, I would vote for an
> alternate name service provider which can be selected if rfc
> compliant behavior is needed.
I agree with the other points.
There is a pre-existing alternative
Put the relevant part of the test in try-catch. If you get OOME skip / ignore.
If you get NASE, then you have a regression.
--
Sent from my mobile device.
Kurchi Hazra wrote:
>
>
>
>Hi,
>
>In HttpUrlConnection, if the chunk length is set to Integer.MAX_VALUE,
>our code was trying to initializ
Hello,
I discovered some unexpected behavior in how Java chooses cipher suites for
SSL/TLS. I wanted to know if its method of cipher suite selection is
documented somewhere so I could understand why it's not working right for me
in certain cases. Notably, if I configure this preference list:
On Thu, May 09, 2013 at 02:11:22PM -0700, Matthew Hall wrote:
> Brian,
>
> That option is very new and non-standard so it doesn't appear anywhere in the
> JDK code.
>
> I think you'll have to make a native library, and use this method:
>
> http://stackov
On Thu, May 09, 2013 at 01:49:02PM -0700, Brian Call wrote:
> Is there any way to make use of a non-standard socket option in Java? Having
> spoken with Neil Horman lead networking developer over at Red Hat, he
> mentioned that by passing in the socket option IP_MULTICAST_ALL with a value
> of '
On Wed, May 08, 2013 at 04:06:10PM -0700, Kurchi Hazra wrote:
> com.sun.net.httpServer uses a selector to get notified about interesting
> events (such as arrival of a new connection, or data available to read
> on an existing connection when using keep-alive), but imposes a timeout of
> 1000 ms on
On Thu, Mar 28, 2013 at 07:11:28PM +0100, Anthony Vanelverdinghe wrote:
> As a conclusion, I believe the SCEP draft should be updated to
> mention the correct Content-Type in case of POST requests.
Good analysis, I agree. I'll see if I can get it corrected.
It would still be nice if there were a
rds
>
> Anthony
>
>
>Op 27/03/2013 18:25, Rob McKenna schreef:
>> HI Matthew,
>>
>> On the face of it this makes sense. I don't have time to dig into it
>> this week, but I'll get stuck into it next week and get a fix
>together.
>>
into it next week and get a fix
> together.
>
> -Rob
>
> On 27/03/13 00:42, Matthew Hall wrote:
> >Forgot to include, offending code in HttpURLConnection:
> >
> >if (!method.equals("PUT") && (poster != null || streaming()))
> >
Tue, Mar 26, 2013 at 05:33:15PM -0700, Matthew Hall wrote:
> Hello,
>
> I was working on a situation which was similar to the situation described in
> this bug which was supposedly fixed in Java 5 and Java 6:
>
> http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6369510
>
not need to set this content-type for GET requests."
To me this means, the code should not be setting the Content-Type to anything,
on any type of request, because it will cause problems across the board.
So I think that the test and the bug fix do not actually fix the original bug
correctly, and the test needs to be fixed so it will work right on an IPv6
based system.
Thoughts?
Matthew Hall.
26 matches
Mail list logo
