Class NetSocket
- java.lang.Object
-
- io.vertx.reactivex.core.net.NetSocket
-
- All Implemented Interfaces:
ReadStream<Buffer>,StreamBase,WriteStream<Buffer>
public class NetSocket extends Object implements ReadStream<Buffer>, WriteStream<Buffer>
Represents a socket-like interface to a TCP connection on either the client or the server side.Instances of this class are created on the client side by an
NetClientwhen a connection to a server is made, or on the server side by aNetServerwhen a server accepts a connection.It implements both and so it can be used with
NOTE: This class has been automatically generated from thePipeto pipe data with flow control.originalnon RX-ified interface using Vert.x codegen.
-
-
Field Summary
Fields Modifier and Type Field Description static TypeArg<NetSocket>__TYPE_ARG
-
Method Summary
All Methods Static Methods Instance Methods Concrete Methods Modifier and Type Method Description StringapplicationLayerProtocol()voidclose()Close the NetSocket and notify thehandlerwhen the operation completes.voidclose(Handler<AsyncResult<Void>> handler)Close the NetSocket and notify thehandlerwhen the operation completes.NetSocketcloseHandler(Handler<Void> handler)Set a handler that will be called when the NetSocket is closedNetSocketdrainHandler(Handler<Void> handler)Set a drain handler on the stream.voidend()voidend(Handler<AsyncResult<Void>> handler)voidend(Buffer data)Same as but with anhandlercalled when the operation completesvoidend(Buffer data, Handler<AsyncResult<Void>> handler)Same as but with anhandlercalled when the operation completesNetSocketendHandler(Handler<Void> endHandler)This handler might be called after the close handler when the socket is paused and there are still buffers to deliver.booleanequals(Object o)NetSocketexceptionHandler(Handler<Throwable> handler)Set an exception handler on the read stream.NetSocketfetch(long amount)Fetch the specifiedamountof elements.NetSocketgetDelegate()NetSockethandler(Handler<Buffer> handler)Set a data handler.inthashCode()StringindicatedServerName()Returns the SNI server name presented during the SSL handshake by the client.booleanisSsl()SocketAddresslocalAddress()SocketAddresslocalAddress(boolean real)static NetSocketnewInstance(NetSocket arg)NetSocketpause()Pause theReadStream, it sets the buffer infetchmode and clears the actual demand.Pipe<Buffer>pipe()Pause this stream and return a to transfer the elements of this stream to a destination .voidpipeTo(WriteStream<Buffer> dst)Pipe thisReadStreamto theWriteStream.voidpipeTo(WriteStream<Buffer> dst, Handler<AsyncResult<Void>> handler)Pipe thisReadStreamto theWriteStream.SocketAddressremoteAddress()SocketAddressremoteAddress(boolean real)NetSocketresume()Resume reading, and sets the buffer inflowingmode.io.reactivex.CompletablerxClose()Close the NetSocket and notify thehandlerwhen the operation completes.io.reactivex.CompletablerxEnd()io.reactivex.CompletablerxEnd(Buffer data)Same as but with anhandlercalled when the operation completesio.reactivex.CompletablerxPipeTo(WriteStream<Buffer> dst)Pipe thisReadStreamto theWriteStream.io.reactivex.CompletablerxSendFile(String filename)Same assendFile(java.lang.String, io.vertx.core.Handler<io.vertx.core.AsyncResult<java.lang.Void>>)but also takes a handler that will be called when the send has completed or a failure has occurredio.reactivex.CompletablerxSendFile(String filename, long offset)Same assendFile(java.lang.String, io.vertx.core.Handler<io.vertx.core.AsyncResult<java.lang.Void>>)but also takes a handler that will be called when the send has completed or a failure has occurredio.reactivex.CompletablerxSendFile(String filename, long offset, long length)Same assendFile(java.lang.String, io.vertx.core.Handler<io.vertx.core.AsyncResult<java.lang.Void>>)but also takes a handler that will be called when the send has completed or a failure has occurredio.reactivex.CompletablerxUpgradeToSsl()Upgrade channel to use SSL/TLS.io.reactivex.CompletablerxUpgradeToSsl(String serverName)Upgrade channel to use SSL/TLS.io.reactivex.CompletablerxWrite(Buffer message)LikeWriteStream.write(T, io.vertx.core.Handler<io.vertx.core.AsyncResult<java.lang.Void>>)but with anhandlercalled when the message has been written or failed to be written.io.reactivex.CompletablerxWrite(String str)Same aswrite(java.lang.String, io.vertx.core.Handler<io.vertx.core.AsyncResult<java.lang.Void>>)but with anhandlercalled when the operation completesio.reactivex.CompletablerxWrite(String str, String enc)Same aswrite(java.lang.String, io.vertx.core.Handler<io.vertx.core.AsyncResult<java.lang.Void>>)but with anhandlercalled when the operation completesNetSocketsendFile(String filename)Same assendFile(java.lang.String, io.vertx.core.Handler<io.vertx.core.AsyncResult<java.lang.Void>>)but also takes a handler that will be called when the send has completed or a failure has occurredNetSocketsendFile(String filename, long offset)Same assendFile(java.lang.String, io.vertx.core.Handler<io.vertx.core.AsyncResult<java.lang.Void>>)but also takes a handler that will be called when the send has completed or a failure has occurredNetSocketsendFile(String filename, long offset, long length)Same assendFile(java.lang.String, io.vertx.core.Handler<io.vertx.core.AsyncResult<java.lang.Void>>)but also takes a handler that will be called when the send has completed or a failure has occurredNetSocketsendFile(String filename, long offset, long length, Handler<AsyncResult<Void>> resultHandler)Same assendFile(java.lang.String, io.vertx.core.Handler<io.vertx.core.AsyncResult<java.lang.Void>>)but also takes a handler that will be called when the send has completed or a failure has occurredNetSocketsendFile(String filename, long offset, Handler<AsyncResult<Void>> resultHandler)Same assendFile(java.lang.String, io.vertx.core.Handler<io.vertx.core.AsyncResult<java.lang.Void>>)but also takes a handler that will be called when the send has completed or a failure has occurredNetSocketsendFile(String filename, Handler<AsyncResult<Void>> resultHandler)Same assendFile(java.lang.String, io.vertx.core.Handler<io.vertx.core.AsyncResult<java.lang.Void>>)but also takes a handler that will be called when the send has completed or a failure has occurredNetSocketsetWriteQueueMaxSize(int maxSize)Set the maximum size of the write queue tomaxSize.SSLSessionsslSession()io.reactivex.Flowable<Buffer>toFlowable()io.reactivex.Observable<Buffer>toObservable()WriteStreamObserver<Buffer>toObserver()StringtoString()WriteStreamSubscriber<Buffer>toSubscriber()NetSocketupgradeToSsl()Upgrade channel to use SSL/TLS.NetSocketupgradeToSsl(Handler<AsyncResult<Void>> handler)Upgrade channel to use SSL/TLS.NetSocketupgradeToSsl(String serverName)Upgrade channel to use SSL/TLS.NetSocketupgradeToSsl(String serverName, Handler<AsyncResult<Void>> handler)Upgrade channel to use SSL/TLS.voidwrite(Buffer message)LikeWriteStream.write(T, io.vertx.core.Handler<io.vertx.core.AsyncResult<java.lang.Void>>)but with anhandlercalled when the message has been written or failed to be written.voidwrite(Buffer message, Handler<AsyncResult<Void>> handler)LikeWriteStream.write(T, io.vertx.core.Handler<io.vertx.core.AsyncResult<java.lang.Void>>)but with anhandlercalled when the message has been written or failed to be written.voidwrite(String str)Same aswrite(java.lang.String, io.vertx.core.Handler<io.vertx.core.AsyncResult<java.lang.Void>>)but with anhandlercalled when the operation completesvoidwrite(String str, Handler<AsyncResult<Void>> handler)Same aswrite(java.lang.String, io.vertx.core.Handler<io.vertx.core.AsyncResult<java.lang.Void>>)but with anhandlercalled when the operation completesvoidwrite(String str, String enc)Same aswrite(java.lang.String, io.vertx.core.Handler<io.vertx.core.AsyncResult<java.lang.Void>>)but with anhandlercalled when the operation completesvoidwrite(String str, String enc, Handler<AsyncResult<Void>> handler)Same aswrite(java.lang.String, io.vertx.core.Handler<io.vertx.core.AsyncResult<java.lang.Void>>)but with anhandlercalled when the operation completesStringwriteHandlerID()When aNetSocketis created, it may register an event handler with the event bus, the ID of that handler is given bywriteHandlerID.booleanwriteQueueFull()This will returntrueif there are more bytes in the write queue than the value set usingsetWriteQueueMaxSize(int)
-
-
-
Method Detail
-
getDelegate
public NetSocket getDelegate()
- Specified by:
getDelegatein interfaceReadStream<Buffer>- Specified by:
getDelegatein interfaceStreamBase- Specified by:
getDelegatein interfaceWriteStream<Buffer>
-
toObservable
public io.reactivex.Observable<Buffer> toObservable()
- Specified by:
toObservablein interfaceReadStream<Buffer>
-
toFlowable
public io.reactivex.Flowable<Buffer> toFlowable()
- Specified by:
toFlowablein interfaceReadStream<Buffer>
-
toObserver
public WriteStreamObserver<Buffer> toObserver()
-
toSubscriber
public WriteStreamSubscriber<Buffer> toSubscriber()
-
end
public void end(Buffer data, Handler<AsyncResult<Void>> handler)
Same as but with anhandlercalled when the operation completes- Specified by:
endin interfaceWriteStream<Buffer>- Parameters:
data-handler-
-
end
public void end(Buffer data)
Same as but with anhandlercalled when the operation completes- Specified by:
endin interfaceWriteStream<Buffer>- Parameters:
data-
-
rxEnd
public io.reactivex.Completable rxEnd(Buffer data)
Same as but with anhandlercalled when the operation completes- Specified by:
rxEndin interfaceWriteStream<Buffer>- Parameters:
data-- Returns:
-
writeQueueFull
public boolean writeQueueFull()
This will returntrueif there are more bytes in the write queue than the value set usingsetWriteQueueMaxSize(int)- Specified by:
writeQueueFullin interfaceWriteStream<Buffer>- Returns:
trueif write queue is full
-
pipe
public Pipe<Buffer> pipe()
Pause this stream and return a to transfer the elements of this stream to a destination . The stream will be resumed when the pipe will be wired to aWriteStream.- Specified by:
pipein interfaceReadStream<Buffer>- Returns:
- a pipe
-
pipeTo
public void pipeTo(WriteStream<Buffer> dst, Handler<AsyncResult<Void>> handler)
Pipe thisReadStreamto theWriteStream.Elements emitted by this stream will be written to the write stream until this stream ends or fails.
Once this stream has ended or failed, the write stream will be ended and the
handlerwill be called with the result.- Specified by:
pipeToin interfaceReadStream<Buffer>- Parameters:
dst- the destination write streamhandler-
-
pipeTo
public void pipeTo(WriteStream<Buffer> dst)
Pipe thisReadStreamto theWriteStream.Elements emitted by this stream will be written to the write stream until this stream ends or fails.
Once this stream has ended or failed, the write stream will be ended and the
handlerwill be called with the result.- Specified by:
pipeToin interfaceReadStream<Buffer>- Parameters:
dst- the destination write stream
-
rxPipeTo
public io.reactivex.Completable rxPipeTo(WriteStream<Buffer> dst)
Pipe thisReadStreamto theWriteStream.Elements emitted by this stream will be written to the write stream until this stream ends or fails.
Once this stream has ended or failed, the write stream will be ended and the
handlerwill be called with the result.- Specified by:
rxPipeToin interfaceReadStream<Buffer>- Parameters:
dst- the destination write stream- Returns:
-
exceptionHandler
public NetSocket exceptionHandler(Handler<Throwable> handler)
Description copied from interface:ReadStreamSet an exception handler on the read stream.- Specified by:
exceptionHandlerin interfaceReadStream<Buffer>- Specified by:
exceptionHandlerin interfaceStreamBase- Specified by:
exceptionHandlerin interfaceWriteStream<Buffer>- Parameters:
handler- the exception handler- Returns:
- a reference to this, so the API can be used fluently
-
handler
public NetSocket handler(Handler<Buffer> handler)
Description copied from interface:ReadStreamSet a data handler. As data is read, the handler will be called with the data.- Specified by:
handlerin interfaceReadStream<Buffer>- Returns:
- a reference to this, so the API can be used fluently
-
pause
public NetSocket pause()
Description copied from interface:ReadStreamPause theReadStream, it sets the buffer infetchmode and clears the actual demand.While it's paused, no data will be sent to the data
handler.- Specified by:
pausein interfaceReadStream<Buffer>- Returns:
- a reference to this, so the API can be used fluently
-
resume
public NetSocket resume()
Description copied from interface:ReadStreamResume reading, and sets the buffer inflowingmode. If theReadStreamhas been paused, reading will recommence on it.- Specified by:
resumein interfaceReadStream<Buffer>- Returns:
- a reference to this, so the API can be used fluently
-
fetch
public NetSocket fetch(long amount)
Description copied from interface:ReadStreamFetch the specifiedamountof elements. If theReadStreamhas been paused, reading will recommence with the specifiedamountof items, otherwise the specifiedamountwill be added to the current stream demand.- Specified by:
fetchin interfaceReadStream<Buffer>- Returns:
- a reference to this, so the API can be used fluently
-
endHandler
public NetSocket endHandler(Handler<Void> endHandler)
This handler might be called after the close handler when the socket is paused and there are still buffers to deliver.
- Specified by:
endHandlerin interfaceReadStream<Buffer>- Parameters:
endHandler-- Returns:
-
setWriteQueueMaxSize
public NetSocket setWriteQueueMaxSize(int maxSize)
Description copied from interface:WriteStreamSet the maximum size of the write queue tomaxSize. You will still be able to write to the stream even if there is more thanmaxSizeitems in the write queue. This is used as an indicator by classes such asPipeto provide flow control. The value is defined by the implementation of the stream, e.g in bytes for aNetSocket, etc...- Specified by:
setWriteQueueMaxSizein interfaceWriteStream<Buffer>- Parameters:
maxSize- the max size of the write stream- Returns:
- a reference to this, so the API can be used fluently
-
drainHandler
public NetSocket drainHandler(Handler<Void> handler)
Description copied from interface:WriteStreamSet a drain handler on the stream. If the write queue is full, then the handler will be called when the write queue is ready to accept buffers again. SeePipefor an example of this being used.The stream implementation defines when the drain handler, for example it could be when the queue size has been reduced to
maxSize / 2.- Specified by:
drainHandlerin interfaceWriteStream<Buffer>- Parameters:
handler- the handler- Returns:
- a reference to this, so the API can be used fluently
-
writeHandlerID
public String writeHandlerID()
When aNetSocketis created, it may register an event handler with the event bus, the ID of that handler is given bywriteHandlerID.By default, no handler is registered, the feature must be enabled via
NetClientOptionsorNetServerOptions.Given this ID, a different event loop can send a buffer to that event handler using the event bus and that buffer will be received by this instance in its own event loop and written to the underlying connection. This allows you to write data to other connections which are owned by different event loops.
- Returns:
- the write handler ID
-
write
public void write(String str, Handler<AsyncResult<Void>> handler)
Same aswrite(java.lang.String, io.vertx.core.Handler<io.vertx.core.AsyncResult<java.lang.Void>>)but with anhandlercalled when the operation completes- Parameters:
str-handler-
-
write
public void write(String str)
Same aswrite(java.lang.String, io.vertx.core.Handler<io.vertx.core.AsyncResult<java.lang.Void>>)but with anhandlercalled when the operation completes- Parameters:
str-
-
rxWrite
public io.reactivex.Completable rxWrite(String str)
Same aswrite(java.lang.String, io.vertx.core.Handler<io.vertx.core.AsyncResult<java.lang.Void>>)but with anhandlercalled when the operation completes- Parameters:
str-- Returns:
-
write
public void write(String str, String enc, Handler<AsyncResult<Void>> handler)
Same aswrite(java.lang.String, io.vertx.core.Handler<io.vertx.core.AsyncResult<java.lang.Void>>)but with anhandlercalled when the operation completes- Parameters:
str-enc-handler-
-
write
public void write(String str, String enc)
Same aswrite(java.lang.String, io.vertx.core.Handler<io.vertx.core.AsyncResult<java.lang.Void>>)but with anhandlercalled when the operation completes- Parameters:
str-enc-
-
rxWrite
public io.reactivex.Completable rxWrite(String str, String enc)
Same aswrite(java.lang.String, io.vertx.core.Handler<io.vertx.core.AsyncResult<java.lang.Void>>)but with anhandlercalled when the operation completes- Parameters:
str-enc-- Returns:
-
write
public void write(Buffer message, Handler<AsyncResult<Void>> handler)
LikeWriteStream.write(T, io.vertx.core.Handler<io.vertx.core.AsyncResult<java.lang.Void>>)but with anhandlercalled when the message has been written or failed to be written.- Specified by:
writein interfaceWriteStream<Buffer>- Parameters:
message-handler-
-
write
public void write(Buffer message)
LikeWriteStream.write(T, io.vertx.core.Handler<io.vertx.core.AsyncResult<java.lang.Void>>)but with anhandlercalled when the message has been written or failed to be written.- Specified by:
writein interfaceWriteStream<Buffer>- Parameters:
message-
-
rxWrite
public io.reactivex.Completable rxWrite(Buffer message)
LikeWriteStream.write(T, io.vertx.core.Handler<io.vertx.core.AsyncResult<java.lang.Void>>)but with anhandlercalled when the message has been written or failed to be written.- Specified by:
rxWritein interfaceWriteStream<Buffer>- Parameters:
message-- Returns:
-
sendFile
public NetSocket sendFile(String filename, Handler<AsyncResult<Void>> resultHandler)
Same assendFile(java.lang.String, io.vertx.core.Handler<io.vertx.core.AsyncResult<java.lang.Void>>)but also takes a handler that will be called when the send has completed or a failure has occurred- Parameters:
filename- file name of the file to sendresultHandler- handler- Returns:
- a reference to this, so the API can be used fluently
-
sendFile
public NetSocket sendFile(String filename)
Same assendFile(java.lang.String, io.vertx.core.Handler<io.vertx.core.AsyncResult<java.lang.Void>>)but also takes a handler that will be called when the send has completed or a failure has occurred- Parameters:
filename- file name of the file to send- Returns:
- a reference to this, so the API can be used fluently
-
rxSendFile
public io.reactivex.Completable rxSendFile(String filename)
Same assendFile(java.lang.String, io.vertx.core.Handler<io.vertx.core.AsyncResult<java.lang.Void>>)but also takes a handler that will be called when the send has completed or a failure has occurred- Parameters:
filename- file name of the file to send- Returns:
- a reference to this, so the API can be used fluently
-
sendFile
public NetSocket sendFile(String filename, long offset, Handler<AsyncResult<Void>> resultHandler)
Same assendFile(java.lang.String, io.vertx.core.Handler<io.vertx.core.AsyncResult<java.lang.Void>>)but also takes a handler that will be called when the send has completed or a failure has occurred- Parameters:
filename- file name of the file to sendoffset- offsetresultHandler- handler- Returns:
- a reference to this, so the API can be used fluently
-
sendFile
public NetSocket sendFile(String filename, long offset)
Same assendFile(java.lang.String, io.vertx.core.Handler<io.vertx.core.AsyncResult<java.lang.Void>>)but also takes a handler that will be called when the send has completed or a failure has occurred- Parameters:
filename- file name of the file to sendoffset- offset- Returns:
- a reference to this, so the API can be used fluently
-
rxSendFile
public io.reactivex.Completable rxSendFile(String filename, long offset)
Same assendFile(java.lang.String, io.vertx.core.Handler<io.vertx.core.AsyncResult<java.lang.Void>>)but also takes a handler that will be called when the send has completed or a failure has occurred- Parameters:
filename- file name of the file to sendoffset- offset- Returns:
- a reference to this, so the API can be used fluently
-
sendFile
public NetSocket sendFile(String filename, long offset, long length, Handler<AsyncResult<Void>> resultHandler)
Same assendFile(java.lang.String, io.vertx.core.Handler<io.vertx.core.AsyncResult<java.lang.Void>>)but also takes a handler that will be called when the send has completed or a failure has occurred- Parameters:
filename- file name of the file to sendoffset- offsetlength- lengthresultHandler- handler- Returns:
- a reference to this, so the API can be used fluently
-
sendFile
public NetSocket sendFile(String filename, long offset, long length)
Same assendFile(java.lang.String, io.vertx.core.Handler<io.vertx.core.AsyncResult<java.lang.Void>>)but also takes a handler that will be called when the send has completed or a failure has occurred- Parameters:
filename- file name of the file to sendoffset- offsetlength- length- Returns:
- a reference to this, so the API can be used fluently
-
rxSendFile
public io.reactivex.Completable rxSendFile(String filename, long offset, long length)
Same assendFile(java.lang.String, io.vertx.core.Handler<io.vertx.core.AsyncResult<java.lang.Void>>)but also takes a handler that will be called when the send has completed or a failure has occurred- Parameters:
filename- file name of the file to sendoffset- offsetlength- length- Returns:
- a reference to this, so the API can be used fluently
-
remoteAddress
public SocketAddress remoteAddress()
- Returns:
- the remote address for this connection, possibly
null(e.g a server bound on a domain socket). IfuseProxyProtocolis set totrue, the address returned will be of the actual connecting client.
-
remoteAddress
public SocketAddress remoteAddress(boolean real)
- Parameters:
real-- Returns:
-
localAddress
public SocketAddress localAddress()
- Returns:
- the local address for this connection, possibly
null(e.g a server bound on a domain socket) IfuseProxyProtocolis set totrue, the address returned will be of the proxy.
-
localAddress
public SocketAddress localAddress(boolean real)
- Parameters:
real-- Returns:
-
end
public void end(Handler<AsyncResult<Void>> handler)
- Specified by:
endin interfaceWriteStream<Buffer>- Parameters:
handler-
-
end
public void end()
- Specified by:
endin interfaceWriteStream<Buffer>
-
rxEnd
public io.reactivex.Completable rxEnd()
- Specified by:
rxEndin interfaceWriteStream<Buffer>- Returns:
-
close
public void close(Handler<AsyncResult<Void>> handler)
Close the NetSocket and notify thehandlerwhen the operation completes.- Parameters:
handler-
-
close
public void close()
Close the NetSocket and notify thehandlerwhen the operation completes.
-
rxClose
public io.reactivex.Completable rxClose()
Close the NetSocket and notify thehandlerwhen the operation completes.- Returns:
-
closeHandler
public NetSocket closeHandler(Handler<Void> handler)
Set a handler that will be called when the NetSocket is closed- Parameters:
handler- the handler- Returns:
- a reference to this, so the API can be used fluently
-
upgradeToSsl
public NetSocket upgradeToSsl(Handler<AsyncResult<Void>> handler)
Upgrade channel to use SSL/TLS. Be aware that for this to work SSL must be configured.- Parameters:
handler- the handler will be notified when it's upgraded- Returns:
- a reference to this, so the API can be used fluently
-
upgradeToSsl
public NetSocket upgradeToSsl()
Upgrade channel to use SSL/TLS. Be aware that for this to work SSL must be configured.- Returns:
- a reference to this, so the API can be used fluently
-
rxUpgradeToSsl
public io.reactivex.Completable rxUpgradeToSsl()
Upgrade channel to use SSL/TLS. Be aware that for this to work SSL must be configured.- Returns:
- a reference to this, so the API can be used fluently
-
upgradeToSsl
public NetSocket upgradeToSsl(String serverName, Handler<AsyncResult<Void>> handler)
Upgrade channel to use SSL/TLS. Be aware that for this to work SSL must be configured.- Parameters:
serverName- the server namehandler- the handler will be notified when it's upgraded- Returns:
- a reference to this, so the API can be used fluently
-
upgradeToSsl
public NetSocket upgradeToSsl(String serverName)
Upgrade channel to use SSL/TLS. Be aware that for this to work SSL must be configured.- Parameters:
serverName- the server name- Returns:
- a reference to this, so the API can be used fluently
-
rxUpgradeToSsl
public io.reactivex.Completable rxUpgradeToSsl(String serverName)
Upgrade channel to use SSL/TLS. Be aware that for this to work SSL must be configured.- Parameters:
serverName- the server name- Returns:
- a reference to this, so the API can be used fluently
-
isSsl
public boolean isSsl()
- Returns:
- true if this
NetSocketis encrypted via SSL/TLS.
-
indicatedServerName
public String indicatedServerName()
Returns the SNI server name presented during the SSL handshake by the client.- Returns:
- the indicated server name
-
applicationLayerProtocol
public String applicationLayerProtocol()
- Returns:
- the application-level protocol negotiated during the TLS handshake
-
sslSession
public SSLSession sslSession()
- Returns:
- SSLSession associated with the underlying socket. Returns null if connection is not SSL.
-
-