* The connect() function defined in this crate will automatically follow redirecting responses. * Adds Error::Redirection, which is a special case of Error::Http that extracts the redirection target from the response headers, and stores it in the error object. Client implementations that build upon tungstenite can use this to implement redirecting. * A catch-all solution for redirects is not possible due to the abstraction transforming socket types to Read + Write, implementations that use the client_* methods need to handle redirections themselves.pull/148/head
parent
2e711fb6fd
commit
6bce14fa26
Loading…
Reference in new issue