https://github.com/paypal/squbs/blob/82ef1b1b6bf1f91cb64ba589554f22505a91a4d6/squbs-pipeline/src/main/scala/org/squbs/pipeline/RequestContext.scala#L48

This cast can fail. It is worrisome because a client would normally expect the Failure to be some kind of HTTP thing.

AFAIK, AKKA only has the Scala implementation for the Java-based abstract HttpResponse, but we should still address this

Both have definitions for system that clash when used together as observed here.

Not sure what the best way forward is. Is there a 2.5/2.6 compatible way of testing typed actors?

Currently websockets are unsupported:

class SttpBackendStub[F[_], S] private (
    monad: MonadError[F],
    matchers: PartialFunction[Request[_, _], F[Response[_]]],
    fallback: Option[SttpBackend[F, S, NothingT]]
) extends SttpBackend[F, S, NothingT] { // TODO

(note the TODO for the NothingT type parameter which specifies what kind of websockets are supported).

The bac

Akka HTTP releases are not tied to a particular Akka version (i.e. the 10.1.x HTTP releases are compatible with the 2.5.x Akka releases) and the user is responsible of providing the actual akka/akka-stream version to be used.

Since this library is mainly tied to a particular akka-http version, it would make sense to mark the other non http related dependencies as provided.

This way a user wa

endpoint:

• auth.md
• basics.md
• codecs.md
• customtypes.md
• forms.md
• integrations.md
• ios.md
• json.md
• statuscodes.md
• validation.md

server:

• akkahttp.md
• debugging.md
• errors.md
• finatra.md
• http4s.md
• logic.md
• options.md
• play.md

Others:

• testing.md
• sttp.md
• index.

Hello,
I'm interested in using this project, but there are still some obscure undocumented aspects. The first one is the schedule method in the RefreshTokenStorage. Can you please clarify what is this for and how is it intended to be implemented?
Also the after parameter should probably be a FiniteDuration rather than simply Duration, should it not?
Is there a plan to work on some bet

I see that x-server-raw-response is available to expose the underlying to users, allowing deeper customization of response.

I was wondering if it's possible to expose a similar interface for request as well? So that we can utilize some predefined functions by akka-http. For example, extractClientIP.

Not a huge deal and is blocking anything, since we can simply replicate all these funct

Short description

In server-side
It should mention the HandlerFactory.
e.g
When do not using metadata, use GreeterServiceHandlerFactory.create().
When using metadata, use `GreeterServicePower

Maybe in the “Community” page?

in https://github.com/lomigmegard/akka-http-cors/blob/master/akka-http-cors/src/main/scala/ch/megard/akka/http/cors/CorsDirectives.scala#L126

Non preflight request is being rejected because it came from an unknown origin

correct behaviour: Non preflight requests from unknown origins should not be rejected

Reported by @craigupson

in this section: https://doc.akka.io/docs/akka-management/current/bootstrap/details.html#bootstrap-process

Sentence:
'If discovery returns the same Contact Points for the contact-point-discovery.stable-margin. '

isn't complete and is ambiguous

As Otoroshi now supports HTTP/2, we should be able to proxy gRPC calls. That would be a great feature for Otoroshi

Linked akka-http issues

• akka/akka-http@c05d47f
• akka/akka-http#1843
• akka/akka-http#530
• akka/akka-http#1857
• https://github.com/akka/

Add special directive allowing to automatically apply CORS rules according to implicit config

An example is provided on how to use standard assets, but it would be great to show how to serve versioned assets using something like https://github.com/sbt/sbt-digest

@patrox 3 days ago
Is there an option to update the image file (docs/src/main/paradox/images/hello-akka-http.png) so it reflects the Paths from here ?

Examples are always the best way to understand something as prose is usually full of ambiguity and other problems. Adding the swagger.json and/or swagger.yaml would be a good way to make this example more complete and useful.

Capture some documentation in the README.md in a new section about the new MergeHub and BroadcastHub stages that's used in this example

Akka HTTP docs regarding HTTPS point to ssl-config documentation where example config is

ssl-config.ssl {
  trustManager = {
    ...
  }
}

The .ssl part is invalid and should no

Since swakka is built on akka-http-10.1.4 it will pull akka-2.5 as dependency (when run with JDK11) akka release notes, would it be possible to cross-compile swakka for those who are stuck with akka 2.4?