Uploaded image for project: 'JDK'
  1. JDK
  2. JDK-6571950

SSLSocket(raddr, rport, laddr, lport) allows null as laddr that spec doesn't reflect

    Details

    • Subcomponent:
    • Resolved In Build:
      b27
    • CPU:
      generic
    • OS:
      generic
    • Verification:
      Verified

      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)

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                xuelei Xue-Lei Fan
                Reporter:
                dgubkin Dmitriy Gubkin (Inactive)
              • Votes:
                0 Vote for this issue
                Watchers:
                0 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:
                  Imported:
                  Indexed: