JDK-8133196 : HTTPS hostname invalid issue with InetAddress
  • Type: Bug
  • Component: core-libs
  • Sub-Component: java.net
  • Affected Version: 7u85
  • Priority: P3
  • Status: Closed
  • Resolution: Fixed
  • Submitted: 2015-08-07
  • Updated: 2021-01-06
  • Resolved: 2015-09-01
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 6 JDK 7 JDK 8 JDK 9
6u105Fixed 7u85Fixed 8u51Fixed 9 b89Fixed
Related Reports
Duplicate :  
Relates :  
Description
Submitter is making a SSL connection and is seeing regression in 7u85.  In both cases they are not using an IP literal address. They are making calls with FQDNs. 

Using the new system property : -Djdk.tls.trustNameService=true resolves their issue. 
We need to debug why a non-IP literal address is encountering this issue.
Comments
No issues with the recent nightly. SQE OK to take the regression bug fix to CPU15_04.
03-09-2015

JDK-8132662 seems related to this issue. Use of InetAddress in socket connection has behavioural change.
18-08-2015