[12] RFR: two small javadoc fixes

[Jonathan Gibbons]

Brian,

You get the problem outside the proxied network as well; the problem is 
that the root certificate used by the DoD is not supported by some 
browsers. It needs to be fixed either by the US Navy or by the browsers. 
Either way, it's nothing we can fix, although now we understand the root 
cause, we can work around the issue in our link checker.

-- Jon


On 11/29/18 12:25 PM, Brian Burkhalter wrote:
> Hi Naoto,
>
> Indeed for the Navy links, inside the proxied network I get a “your connection is not secure” page in Firefox but you indicate this is out of our control. Therefore this looks OK.
>
> Brian
>
>> On Nov 29, 2018, at 12:11 PM, naoto.sato at oracle.com wrote:
>>
>> Please review the URL fixes to the following issues:
>>
>> https://bugs.openjdk.java.net/browse/JDK-8212870 <https://bugs.openjdk.java.net/browse/JDK-8212870> : Broken links for www.usno.navy.mil <http://www.usno.navy.mil/>
>> https://bugs.openjdk.java.net/browse/JDK-8212878 <https://bugs.openjdk.java.net/browse/JDK-8212878> : host in ftp: link not found
>>
>> The proposed changesets are located at:
>>
>> http://cr.openjdk.java.net/~naoto/8212870/webrev.00/ <http://cr.openjdk.java.net/~naoto/8212870/webrev.00/>
>> http://cr.openjdk.java.net/~naoto/8212878/webrev.00/ <http://cr.openjdk.java.net/~naoto/8212878/webrev.00/>
>>
>> For the former java.util.Date issue (8212870), it is not actually a broken link, but the root CA at the website is not validated, thus the browsers will complain. There's nothing we can do from the javadoc view point to resolve this. Just replaced the URL protocol to "https" from "http". The latter one is simply replacing the obsolete ftp URL to the correct one.