Creates a akka.stream.javadsl.Source of IncomingConnection instances which represents a prospective HTTP server binding
on the given endpoint
.
Creates a akka.stream.javadsl.Source of IncomingConnection instances which represents a prospective HTTP server binding
on the given endpoint
.
If the given port is 0 the resulting source can be materialized several times. Each materialization will then be assigned a new local port by the operating system, which can then be retrieved by the materialized ServerBinding.
If the given port is non-zero subsequent materialization attempts of the produced source will immediately fail, unless the first materialization has already been unbound. Unbinding can be triggered via the materialized ServerBinding.
The server will be bound using HTTPS if the ConnectHttp object is configured with an HttpsConnectionContext, or the defaultServerHttpContext has been configured to be an HttpsConnectionContext.
Creates a akka.stream.javadsl.Source of IncomingConnection instances which represents a prospective HTTP server binding
on the given endpoint
.
Creates a akka.stream.javadsl.Source of IncomingConnection instances which represents a prospective HTTP server binding
on the given endpoint
.
If the given port is 0 the resulting source can be materialized several times. Each materialization will then be assigned a new local port by the operating system, which can then be retrieved by the materialized ServerBinding.
If the given port is non-zero subsequent materialization attempts of the produced source will immediately fail, unless the first materialization has already been unbound. Unbinding can be triggered via the materialized ServerBinding.
The server will be bound using HTTPS if the ConnectHttp object is configured with an HttpsConnectionContext, or the defaultServerHttpContext has been configured to be an HttpsConnectionContext.
Creates a akka.stream.javadsl.Source of IncomingConnection instances which represents a prospective HTTP server binding
on the given endpoint
.
Creates a akka.stream.javadsl.Source of IncomingConnection instances which represents a prospective HTTP server binding
on the given endpoint
.
If the given port is 0 the resulting source can be materialized several times. Each materialization will then be assigned a new local port by the operating system, which can then be retrieved by the materialized ServerBinding.
If the given port is non-zero subsequent materialization attempts of the produced source will immediately fail, unless the first materialization has already been unbound. Unbinding can be triggered via the materialized ServerBinding.
The server will be bound using HTTPS if the ConnectHttp object is configured with an HttpsConnectionContext, or the defaultServerHttpContext has been configured to be an HttpsConnectionContext.
Convenience method which starts a new HTTP server at the given endpoint and uses the given handler
akka.stream.javadsl.Flow for processing all incoming connections.
Convenience method which starts a new HTTP server at the given endpoint and uses the given handler
akka.stream.javadsl.Flow for processing all incoming connections.
The number of concurrently accepted connections can be configured by overriding
the akka.http.server.max-connections
setting. Please see the documentation in the reference.conf for more
information about what kind of guarantees to expect.
The server will be bound using HTTPS if the ConnectHttp object is configured with an HttpsConnectionContext, or the defaultServerHttpContext has been configured to be an HttpsConnectionContext.
Convenience method which starts a new HTTP server at the given endpoint and uses the given handler
akka.stream.javadsl.Flow for processing all incoming connections.
Convenience method which starts a new HTTP server at the given endpoint and uses the given handler
akka.stream.javadsl.Flow for processing all incoming connections.
The number of concurrently accepted connections can be configured by overriding
the akka.http.server.max-connections
setting. Please see the documentation in the reference.conf for more
information about what kind of guarantees to expect.
The server will be bound using HTTPS if the ConnectHttp object is configured with an HttpsConnectionContext, or the defaultServerHttpContext has been configured to be an HttpsConnectionContext.
Convenience method which starts a new HTTP server at the given endpoint and uses the given handler
akka.stream.javadsl.Flow for processing all incoming connections.
Convenience method which starts a new HTTP server at the given endpoint and uses the given handler
akka.stream.javadsl.Flow for processing all incoming connections.
The number of concurrently accepted connections can be configured by overriding
the akka.http.server.max-connections
setting. Please see the documentation in the reference.conf for more
information about what kind of guarantees to expect.
The server will be bound using HTTPS if the ConnectHttp object is configured with an HttpsConnectionContext, or the defaultServerHttpContext has been configured to be an HttpsConnectionContext.
Convenience method which starts a new HTTP server at the given endpoint and uses the given handler
akka.stream.javadsl.Flow for processing all incoming connections.
Convenience method which starts a new HTTP server at the given endpoint and uses the given handler
akka.stream.javadsl.Flow for processing all incoming connections.
The number of concurrently accepted connections can be configured by overriding
the akka.http.server.max-connections
setting. Please see the documentation in the reference.conf for more
information about what kind of guarantees to expect.
The server will be bound using HTTPS if the ConnectHttp object is configured with an HttpsConnectionContext, or the defaultServerHttpContext has been configured to be an HttpsConnectionContext.
Convenience method which starts a new HTTP server at the given endpoint and uses the given handler
akka.stream.javadsl.Flow for processing all incoming connections.
Convenience method which starts a new HTTP server at the given endpoint and uses the given handler
akka.stream.javadsl.Flow for processing all incoming connections.
The number of concurrently accepted connections can be configured by overriding
the akka.http.server.max-connections
setting. Please see the documentation in the reference.conf for more
information about what kind of guarantees to expect.
The server will be bound using HTTPS if the ConnectHttp object is configured with an HttpsConnectionContext, or the defaultServerHttpContext has been configured to be an HttpsConnectionContext.
Convenience method which starts a new HTTP server at the given endpoint and uses the given handler
akka.stream.javadsl.Flow for processing all incoming connections.
Convenience method which starts a new HTTP server at the given endpoint and uses the given handler
akka.stream.javadsl.Flow for processing all incoming connections.
The number of concurrently accepted connections can be configured by overriding
the akka.http.server.max-connections
setting. Please see the documentation in the reference.conf for more
information about what kind of guarantees to expect.
The server will be bound using HTTPS if the ConnectHttp object is configured with an HttpsConnectionContext, or the defaultServerHttpContext has been configured to be an HttpsConnectionContext.
Returns a akka.stream.javadsl.Flow which dispatches incoming HTTP requests to the per-ActorSystem pool of outgoing HTTP connections to the given target host endpoint.
Returns a akka.stream.javadsl.Flow which dispatches incoming HTTP requests to the per-ActorSystem pool of outgoing HTTP connections to the given target host endpoint. For every ActorSystem, target host and pool configuration a separate connection pool is maintained. The HTTP layer transparently manages idle shutdown and restarting of connections pools as configured. The returned akka.stream.javadsl.Flow instances therefore remain valid throughout the lifetime of the application.
The internal caching logic guarantees that there will never be more than a single pool running for the given target host endpoint and configuration (in this ActorSystem).
Since the underlying transport usually comprises more than a single connection the produced flow might generate
responses in an order that doesn't directly match the consumed requests.
For example, if two requests A and B enter the flow in that order the response for B might be produced before the
response for A.
In order to allow for easy response-to-request association the flow takes in a custom, opaque context
object of type T
from the application which is emitted together with the corresponding response.
To configure additional settings for the pool (and requests made using it),
use the akka.http.host-connection-pool
config section or pass in a ConnectionPoolSettings explicitly.
Returns a akka.stream.javadsl.Flow which dispatches incoming HTTP requests to the per-ActorSystem pool of outgoing HTTP connections to the given target host endpoint.
Returns a akka.stream.javadsl.Flow which dispatches incoming HTTP requests to the per-ActorSystem pool of outgoing HTTP connections to the given target host endpoint. For every ActorSystem, target host and pool configuration a separate connection pool is maintained. The HTTP layer transparently manages idle shutdown and restarting of connections pools as configured. The returned akka.stream.javadsl.Flow instances therefore remain valid throughout the lifetime of the application.
The internal caching logic guarantees that there will never be more than a single pool running for the given target host endpoint and configuration (in this ActorSystem).
Since the underlying transport usually comprises more than a single connection the produced flow might generate
responses in an order that doesn't directly match the consumed requests.
For example, if two requests A and B enter the flow in that order the response for B might be produced before the
response for A.
In order to allow for easy response-to-request association the flow takes in a custom, opaque context
object of type T
from the application which is emitted together with the corresponding response.
Returns a akka.stream.javadsl.Flow which dispatches incoming HTTP requests to the per-ActorSystem pool of outgoing HTTP connections to the given target host endpoint.
Returns a akka.stream.javadsl.Flow which dispatches incoming HTTP requests to the per-ActorSystem pool of outgoing HTTP connections to the given target host endpoint. For every ActorSystem, target host and pool configuration a separate connection pool is maintained. The HTTP layer transparently manages idle shutdown and restarting of connections pools as configured. The returned akka.stream.javadsl.Flow instances therefore remain valid throughout the lifetime of the application.
The internal caching logic guarantees that there will never be more than a single pool running for the given target host endpoint and configuration (in this ActorSystem).
Since the underlying transport usually comprises more than a single connection the produced flow might generate
responses in an order that doesn't directly match the consumed requests.
For example, if two requests A and B enter the flow in that order the response for B might be produced before the
response for A.
In order to allow for easy response-to-request association the flow takes in a custom, opaque context
object of type T
from the application which is emitted together with the corresponding response.
Same as cachedHostConnectionPool but with HTTPS encryption.
Same as cachedHostConnectionPool but with HTTPS encryption.
When an HttpConnectionContext is defined in the given ConnectHttp it will be used, otherwise the default client-side context will be used.
Same as cachedHostConnectionPool but with HTTPS encryption.
Same as cachedHostConnectionPool but with HTTPS encryption.
When an HttpConnectionContext is defined in the given ConnectHttp it will be used, otherwise the default client-side context will be used.
Constructs a client layer stage using the given ClientConnectionSettings.
Constructs a client layer stage using the given akka.http.javadsl.settings.ClientConnectionSettings.
Constructs a client layer stage using the configured default akka.http.javadsl.settings.ClientConnectionSettings.
Gets the current default client-side ConnectionContext.
Gets the current default server-side ConnectionContext – defaults to plain HTTP.
Gets the current default server-side ConnectionContext – defaults to plain HTTP. Can be modified using setDefaultServerHttpContext, and will then apply for servers bound after that call has completed.
Same as newHostConnectionPool but with HTTPS encryption.
Same as newHostConnectionPool but with HTTPS encryption.
The given ConnectionContext will be used for encryption on the connection.
Starts a new connection pool to the given host and configuration and returns a akka.stream.javadsl.Flow which dispatches the requests from all its materializations across this pool.
Starts a new connection pool to the given host and configuration and returns a akka.stream.javadsl.Flow which dispatches the requests from all its materializations across this pool. While the started host connection pool internally shuts itself down automatically after the configured idle timeout it will spin itself up again if more requests arrive from an existing or a new client flow materialization. The returned flow therefore remains usable for the full lifetime of the application.
Since the underlying transport usually comprises more than a single connection the produced flow might generate
responses in an order that doesn't directly match the consumed requests.
For example, if two requests A and B enter the flow in that order the response for B might be produced before the
response for A.
In order to allow for easy response-to-request association the flow takes in a custom, opaque context
object of type T
from the application which is emitted together with the corresponding response.
Starts a new connection pool to the given host and configuration and returns a akka.stream.javadsl.Flow which dispatches the requests from all its materializations across this pool.
Starts a new connection pool to the given host and configuration and returns a akka.stream.javadsl.Flow which dispatches the requests from all its materializations across this pool. While the started host connection pool internally shuts itself down automatically after the configured idle timeout it will spin itself up again if more requests arrive from an existing or a new client flow materialization. The returned flow therefore remains usable for the full lifetime of the application.
Since the underlying transport usually comprises more than a single connection the produced flow might generate
responses in an order that doesn't directly match the consumed requests.
For example, if two requests A and B enter the flow in that order the response for B might be produced before the
response for A.
In order to allow for easy response-to-request association the flow takes in a custom, opaque context
object of type T
from the application which is emitted together with the corresponding response.
Creates a akka.stream.javadsl.Flow representing a prospective HTTP client connection to the given endpoint.
Creates a akka.stream.javadsl.Flow representing a prospective HTTP client connection to the given endpoint. Every materialization of the produced flow will attempt to establish a new outgoing connection.
Creates a akka.stream.javadsl.Flow representing a prospective HTTP client connection to the given endpoint.
Creates a akka.stream.javadsl.Flow representing a prospective HTTP client connection to the given endpoint. Every materialization of the produced flow will attempt to establish a new outgoing connection.
Use the ConnectHttp DSL to configure target host and whether HTTPS should be used.
Creates a akka.stream.javadsl.Flow representing a prospective HTTP client connection to the given endpoint.
Creates a akka.stream.javadsl.Flow representing a prospective HTTP client connection to the given endpoint. Every materialization of the produced flow will attempt to establish a new outgoing connection.
If the hostname is given with an https://
prefix, the default HttpsConnectionContext will be used.
Constructs a server layer stage using the given ServerSettings.
Constructs a server layer stage using the given ServerSettings. The returned akka.stream.javadsl.BidiFlow isn't reusable and
can only be materialized once. The remoteAddress, if provided, will be added as a header to each HttpRequest
this layer produces if the akka.http.server.remote-address-header
configuration option is enabled.
Constructs a server layer stage using the given akka.http.javadsl.settings.ServerSettings.
Constructs a server layer stage using the given akka.http.javadsl.settings.ServerSettings. The returned akka.stream.javadsl.BidiFlow isn't reusable and
can only be materialized once. The remoteAddress
, if provided, will be added as a header to each HttpRequest
this layer produces if the akka.http.server.remote-address-header
configuration option is enabled.
Constructs a server layer stage using the given akka.http.javadsl.settings.ServerSettings.
Constructs a server layer stage using the given akka.http.javadsl.settings.ServerSettings. The returned akka.stream.javadsl.BidiFlow isn't reusable and can only be materialized once.
Constructs a server layer stage using the configured default akka.http.javadsl.settings.ServerSettings.
Constructs a server layer stage using the configured default akka.http.javadsl.settings.ServerSettings. The returned akka.stream.javadsl.BidiFlow isn't reusable and can only be materialized once.
Sets the default client-side ConnectionContext.
Sets the default server-side ConnectionContext.
Sets the default server-side ConnectionContext. If it is an instance of HttpsConnectionContext then the server will be bound using HTTPS.
Triggers an orderly shutdown of all host connections pools currently maintained by the akka.actor.ActorSystem.
Triggers an orderly shutdown of all host connections pools currently maintained by the akka.actor.ActorSystem. The returned future is completed when all pools that were live at the time of this method call have completed their shutdown process.
If existing pool client flows are re-used or new ones materialized concurrently with or after this method call the respective connection pools will be restarted and not contribute to the returned future.
Fires a single HttpRequest across the (cached) host connection pool for the request's effective URI to produce a response future.
Fires a single HttpRequest across the (cached) host connection pool for the request's effective URI to produce a response future.
The given HttpsConnectionContext will be used for encryption if the request is sent to an https endpoint.
Note that the request must have either an absolute URI or a valid Host
header, otherwise
the future will be completed with an error.
Fires a single HttpRequest across the (cached) host connection pool for the request's effective URI to produce a response future.
Fires a single HttpRequest across the (cached) host connection pool for the request's effective URI to produce a response future.
The defaultClientHttpsContext is used to configure TLS for the connection.
Note that the request must have either an absolute URI or a valid Host
header, otherwise
the future will be completed with an error.
Fires a single HttpRequest across the (cached) host connection pool for the request's effective URI to produce a response future.
Fires a single HttpRequest across the (cached) host connection pool for the request's effective URI to produce a response future.
The defaultClientHttpsContext is used to configure TLS for the connection.
Note that the request must have either an absolute URI or a valid Host
header, otherwise
the future will be completed with an error.
Runs a single WebSocket conversation given a Uri and a flow that represents the client side of the WebSocket conversation.
Runs a single WebSocket conversation given a Uri and a flow that represents the client side of the WebSocket conversation.
Runs a single WebSocket conversation given a Uri and a flow that represents the client side of the WebSocket conversation.
The defaultClientHttpsContext is used to configure TLS for the connection.
Runs a single WebSocket conversation given a Uri and a flow that represents the client side of the WebSocket conversation.
Runs a single WebSocket conversation given a Uri and a flow that represents the client side of the WebSocket conversation.
The defaultClientHttpsContext is used to configure TLS for the connection.
Creates a new "super connection pool flow", which routes incoming requests to a (cached) host connection pool depending on their respective effective URIs.
Creates a new "super connection pool flow", which routes incoming requests to a (cached) host connection pool
depending on their respective effective URIs. Note that incoming requests must have either an absolute URI or
a valid Host
header.
The defaultClientHttpsContext is used to configure TLS for the connection.
Since the underlying transport usually comprises more than a single connection the produced flow might generate
responses in an order that doesn't directly match the consumed requests.
For example, if two requests A
and B
enter the flow
in that order the response for B
might be produced before the
response for A
.
In order to allow for easy response-to-request association the flow takes in a custom, opaque context
object of type T
from the application which is emitted together with the corresponding response.
Creates a new "super connection pool flow", which routes incoming requests to a (cached) host connection pool depending on their respective effective URIs.
Creates a new "super connection pool flow", which routes incoming requests to a (cached) host connection pool
depending on their respective effective URIs. Note that incoming requests must have either an absolute URI or
a valid Host
header.
The given HttpsConnectionContext is used to configure TLS for the connection.
Since the underlying transport usually comprises more than a single connection the produced flow might generate
responses in an order that doesn't directly match the consumed requests.
For example, if two requests A
and B
enter the flow
in that order the response for B
might be produced before the
response for A
.
In order to allow for easy response-to-request association the flow takes in a custom, opaque context
object of type T
from the application which is emitted together with the corresponding response.
Creates a new "super connection pool flow", which routes incoming requests to a (cached) host connection pool depending on their respective effective URIs.
Creates a new "super connection pool flow", which routes incoming requests to a (cached) host connection pool
depending on their respective effective URIs. Note that incoming requests must have either an absolute URI or
a valid Host
header.
Since the underlying transport usually comprises more than a single connection the produced flow might generate
responses in an order that doesn't directly match the consumed requests.
For example, if two requests A
and B
enter the flow in that order the response for B
might be produced before the
response for A
.
In order to allow for easy response-to-request association the flow takes in a custom, opaque context
object of type T
from the application which is emitted together with the corresponding response.
Constructs a flow that once materialized establishes a WebSocket connection to the given Uri.
Constructs a flow that once materialized establishes a WebSocket connection to the given Uri.
The layer is not reusable and must only be materialized once.
Constructs a flow that once materialized establishes a WebSocket connection to the given Uri.
Constructs a flow that once materialized establishes a WebSocket connection to the given Uri.
The layer is not reusable and must only be materialized once.
Constructs a WebSocket akka.stream.javadsl.BidiFlow using the configured default ClientConnectionSettings,
configured using the akka.http.client
config section.
Constructs a WebSocket akka.stream.javadsl.BidiFlow using the configured default ClientConnectionSettings,
configured using the akka.http.client
config section.
The layer is not reusable and must only be materialized once.
Constructs a WebSocket akka.stream.javadsl.BidiFlow using the configured default ClientConnectionSettings,
configured using the akka.http.client
config section.
Constructs a WebSocket akka.stream.javadsl.BidiFlow using the configured default ClientConnectionSettings,
configured using the akka.http.client
config section.
The layer is not reusable and must only be materialized once.
Constructs a WebSocket akka.stream.javadsl.BidiFlow.
Constructs a WebSocket akka.stream.javadsl.BidiFlow.
The layer is not reusable and must only be materialized once.
in favor of method that doesn't require materializer. You can just remove the materializer argument.
in favor of method that doesn't require materializer. You can just remove the materializer argument.
in favor of method that doesn't require materializer. You can just remove the materializer argument.
in favor of method that doesn't require materializer. You can just remove the materializer argument.
in favor of method that doesn't require materializer. You can just remove the materializer argument.
in favor of method that doesn't require materializer. You can just remove the materializer argument.
in favor of method that doesn't require materializer. You can just remove the materializer argument.
in favor of method that doesn't require materializer. You can just remove the materializer argument.
in favor of method that doesn't require materializer. You can just remove the materializer argument.
in favor of method that doesn't require materializer. You can just remove the materializer argument.
in favor of method that doesn't require materializer. You can just remove the materializer argument.
in favor of method that doesn't require materializer. You can just remove the materializer argument.
in favor of method that doesn't require materializer. You can just remove the materializer argument.
in favor of method that doesn't require materializer. You can just remove the materializer argument.
in favor of method that doesn't require materializer. You can just remove the materializer argument.
in favor of method that doesn't require materializer. You can just remove the materializer argument.