This week's book giveaway is in the JDBC forum.
We're giving away four copies of Make it so: Java DB Connections & Transactions and have Marcho Behler on-line!
See this thread for details.
The moose likes Sockets and Internet Protocols and the fly likes HTTPS hostname wrong: should be Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login

Win a copy of Make it so: Java DB Connections & Transactions this week in the JDBC forum!
JavaRanch » Java Forums » Java » Sockets and Internet Protocols
Bookmark "HTTPS hostname wrong: should be" Watch "HTTPS hostname wrong: should be" New topic

HTTPS hostname wrong: should be

Jeremy Thornton
Ranch Hand

Joined: Feb 21, 2002
Posts: 91
I'm trying to post data to a secure webserver. If I run the webserver and my client application on the same box then all is ok (using a key created for localhost).
If I generate a key for the webserver for my IP address and then try to hit it from another machine, the handshake seems to go ok until I get a
"HTTPS hostname wrong: should be <my ip address>" (where my ip address is my actual IP address.
In the past when I've seen this error it has been followed by
", but cert says <host>" or something similar.
The IP address used in the public key seems to match the IP I'm specifying as the address "https://my ip address:442/testwebserver".
I'm confused... any suggestions?
I agree. Here's the link:
subject: HTTPS hostname wrong: should be
It's not a secret anymore!