public class OutgoingConnectionBlueprint
extends java.lang.Object
Modifier and Type | Class and Description |
---|---|
static class |
OutgoingConnectionBlueprint.PrepareResponse
This is essentially a three state state machine, it is either 'idle' - waiting for a response to come in
or has seen the start of a response and is waiting for either chunks followed by MessageEnd if chunked
or just MessageEnd in the case of a strict response.
|
static class |
OutgoingConnectionBlueprint.ResponseParsingMerge
A merge that follows this logic:
1.
|
static class |
OutgoingConnectionBlueprint.UnexpectedConnectionClosureException |
Constructor and Description |
---|
OutgoingConnectionBlueprint() |
Modifier and Type | Method and Description |
---|---|
static org.apache.pekko.stream.scaladsl.BidiFlow<HttpRequest,org.apache.pekko.stream.TLSProtocol.SslTlsOutbound,org.apache.pekko.stream.TLSProtocol.SslTlsInbound,HttpResponse,org.apache.pekko.NotUsed> |
apply(Host hostHeader,
ClientConnectionSettings settings,
org.apache.pekko.event.LoggingAdapter log) |
public static org.apache.pekko.stream.scaladsl.BidiFlow<HttpRequest,org.apache.pekko.stream.TLSProtocol.SslTlsOutbound,org.apache.pekko.stream.TLSProtocol.SslTlsInbound,HttpResponse,org.apache.pekko.NotUsed> apply(Host hostHeader, ClientConnectionSettings settings, org.apache.pekko.event.LoggingAdapter log)