The address this connection is connected to. Could be a server or a proxy.

Forces a call to the native implementation of the connection's channel to verify that this channel is still open.

This method should only be called just after an HTTP/1.1 connection is retrieved from the HTTP/1.1 connection pool. It is used to trigger an early detection of the channel state, before handling the connection over to the HTTP stack. It helps minimizing race conditions where the selector manager thread hasn't woken up - or hasn't raised the event, before the connection was retrieved from the pool. It helps reduce the occurrence of "HTTP/1.1 parser received no bytes" exception, when the server closes the connection while it's being taken out of the pool.

This method attempts to read one byte from the underlying channel. Because the connection was in the pool - there should be nothing to read.

If read manages to read a byte off the connection, this is a protocol error: the method closes the connection and returns false. If read returns EOF, the method closes the connection and returns false. If read throws an exception, the method returns false. Otherwise, read returns 0, the channel appears to be still open, and the method returns true.

Returns:boolean

true if the channel appears to be still open.

Closes this connection due to the given cause.

Parameters

cause:Throwable

the cause for which the connection is closed, may be null

Tells whether, or not, this connection is connected to its destination.

Returns the underlying connection flow, if applicable.

Returns:FlowTube

the underlying connection flow, if applicable

Exceptions

IllegalStateException:

if the underlying transport does not expose a single connection flow.

Returns the Origin server against which this connection communicates. Returns null if the connection is a plain connection to a proxy.

Returns:Origin

the Origin server against which this connection communicates. Returns null if the connection is a plain connection to a proxy

This method is used to build a filter that will accept or veto (header-name, value) tuple for transmission on the wire. The filter is applied to the headers when sending the headers to the remote party. Which tuple is accepted/vetoed depends on:

   - whether the connection is a tunnel connection
     [talking to a server through a proxy tunnel]
   - whether the method is CONNECT
     [establishing a CONNECT tunnel through a proxy]
   - whether the request is using a proxy
     (and the connection is not a tunnel)
     [talking to a server through a proxy]
   - whether the request is a direct connection to
     a server (no tunnel, no proxy).

{@return true if the connection flow is finished.

Tells whether, or not, this connection is open.

Tells whether, or not, this connection is proxied. Returns true for tunnel connections, or clear connection to any host through proxy.

Tells whether, or not, this connection is secure ( over SSL )

Returns the address of the proxy used by this connection. Returns the proxy address for tunnel connections, or clear connection to any host through proxy. Returns null otherwise.

Returns the HTTP publisher associated with this connection. May be null if invoked before connecting.