@Deprecated public interface SchemeSocketFactory
|Modifier and Type||Method and Description|
Connects a socket to the target host with the given remote address.
Creates a new, unconnected socket.
Checks whether a socket provides a secure connection.
Socket createSocket(org.apache.http.params.HttpParams params) throws IOException
connectSocket(Socket, InetSocketAddress, InetSocketAddress, HttpParams).
parameters. In most cases these parameters will not be required and will have no effect, as usually socket initialization should take place in the
connectSocket(Socket, InetSocketAddress, InetSocketAddress, HttpParams)method. However, in rare cases one may want to pass additional parameters to this method in order to create a customized
Socketinstance, for instance bound to a SOCKS proxy server.
IOException- if an I/O error occurs while creating the socket
Socket connectSocket(Socket sock, InetSocketAddress remoteAddress, InetSocketAddress localAddress, org.apache.http.params.HttpParams params) throws IOException, UnknownHostException, ConnectTimeoutException
Please note that
HttpInetSocketAddress class should
be used in order to pass the target remote address along with the original
HttpHost value used to resolve the address. The use of
HttpInetSocketAddress can also ensure that no reverse
DNS lookup will be performed if the target remote address was specified
as an IP address.
sock- the socket to connect, as obtained from
nullindicates that a new socket should be created and connected.
remoteAddress- the remote address to connect to.
localAddress- the local address to bind the socket to, or
sockargument if this factory supports a layered protocol.
IOException- if an I/O error occurs
UnknownHostException- if the IP address of the target host can not be determined
ConnectTimeoutException- if the socket cannot be connected within the time limit defined in the
boolean isSecure(Socket sock) throws IllegalArgumentException
connectedby this factory. The factory will not perform I/O operations in this method.
As a rule of thumb, plain sockets are not secure and TLS/SSL sockets are secure. However, there may be application specific deviations. For example, a plain socket to a host in the same intranet ("trusted zone") could be considered secure. On the other hand, a TLS/SSL socket could be considered insecure based on the cipher suite chosen for the connection.
sock- the connected socket to check
trueif the connection of the socket should be considered secure, or
falseif it should not
IllegalArgumentException- if the argument is invalid, for example because it is not a connected socket or was created by a different socket factory. Note that socket factories are not required to check these conditions, they may simply return a default value when called with an invalid socket argument.
Copyright © 1999–2017 The Apache Software Foundation. All rights reserved.