Arnout Engelen
Arnout Engelen
https://github.com/raboof/akka-http-connect-without-checking-cert/blob/0ca55a06afb83b587f592dd97358970502f7b834/Main.scala - yeah, I see what you mean. Of course shipping a `trustfulSslContext` would make things a lot shorter, but we'd have to give it a really scary name to...
https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/X-Forwarded-For doesn't mention allowing a port, but the standardized `Forwarded` header does allow one (https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Forwarded). It might make sense to support a port, but on the other hand, perhaps it's...
That indeed matches what I read at https://docs.microsoft.com/en-us/azure/application-gateway/how-application-gateway-works - would be good to support this, would you be interested in preparing a PR?
I don't have much experience with sttp. A minimal project that shows the problem in isolation and can be used to further diagnose the problem might be a good start?
Nice! It looks like it could use some docs on how to use it, and then perhaps we could link to it from https://doc.akka.io/docs/akka-http/current/extensions.html ?
I don't think I've looked into this before apart from recording the reproducer - I bet we can once we look closer ;)
> Why doesn't PR validation fail on this test? Aren't the tests run on JDK 11? I think PR validation is on jdk8 (and we have jdk11 nightlies)
This seems to succeed now
Oops, indeed I was still on JDK8 here :confused: sorry about the noise.
reported on the Akka side as https://github.com/akka/akka/issues/29957