pub trait TunnelExt: Tunnel + Send {
// Required method
fn forward<'life0, 'async_trait>(
&'life0 mut self,
url: Url,
) -> Pin<Box<dyn Future<Output = Result<(), Error>> + Send + 'async_trait>>
where Self: 'async_trait,
'life0: 'async_trait;
}👎Deprecated: superceded by the
listen_and_forward builder methodExpand description
Extension methods auto-implemented for all tunnel types
Required Methods§
Sourcefn forward<'life0, 'async_trait>(
&'life0 mut self,
url: Url,
) -> Pin<Box<dyn Future<Output = Result<(), Error>> + Send + 'async_trait>>where
Self: 'async_trait,
'life0: 'async_trait,
👎Deprecated: superceded by the listen_and_forward builder method
fn forward<'life0, 'async_trait>(
&'life0 mut self,
url: Url,
) -> Pin<Box<dyn Future<Output = Result<(), Error>> + Send + 'async_trait>>where
Self: 'async_trait,
'life0: 'async_trait,
listen_and_forward builder methodForward incoming tunnel connections to the provided url based on its scheme. This currently supports http, https, tls, and tcp on all platforms, unix sockets on unix platforms, and named pipes on Windows via the “pipe” scheme.
Unix socket URLs can be formatted as unix://path/to/socket or
unix:path/to/socket for relative paths or as unix:///path/to/socket or
unix:/path/to/socket for absolute paths.
Windows named pipe URLs can be formatted as pipe:mypipename or
pipe://host/mypipename. If no host is provided, as with
pipe:///mypipename or pipe:/mypipename, the leading slash will be
preserved.