|
Quick Lists
|
|
Bug ID:
|
6571950
|
|
Votes
|
0
|
|
Synopsis
|
SSLSocket(raddr, rport, laddr, lport) allows null as laddr that spec doesn't reflect
|
|
Category
|
jsse:doc
|
|
Reported Against
|
|
|
Release Fixed
|
7(b27)
|
|
State
|
11-Closed,
Verified,
request for enhancement
|
|
Priority:
|
3-Medium
|
|
Related Bugs
|
6546669
,
6571708
,
6573503
|
|
Submit Date
|
20-JUN-2007
|
|
Description
|
For javax.net.ssl.SSLSocket class
constructor
protected SSLSocket(InetAddress address, int port,
InetAddress clientAddress, int clientPort)
allows passing null as clientAddress. ( in JDK 5, JDK 6, JDK 7 )
It looks like in this case the system will pick up a valid local address for create/bind.
Specification for this constructor doesn't reflect this.
The same promlem is in spec for java.net.Socket class for similar constructor.
But for instance spec in Socket class for method
void bind(SocketAddress bindpoint)
clearly says that:
"If the address is null, then the system will pick up an ephemeral port and a valid local address to bind the socket."
So we need to mention about possibilty of passing null as local_address in case of
constructor
protected SSLSocket(InetAddress address, int port,
InetAddress clientAddress, int clientPort)
and the same for class Socket:
Socket(InetAddress address, int port, InetAddress localAddr, int localPort)
Posted Date : 2007-06-20 19:46:12.0
|
|
Work Around
|
N/A
|
|
Evaluation
|
should add the description that while the local address parameter is null, anyLocalAddress will be used instead.
Posted Date : 2008-04-11 07:58:51.0
|
|
Comments
|
PLEASE NOTE: JDK6 is formerly known as Project Mustang
|
|
|
 |