HttpServer | C Qt 5 HTTP Server | HTTP library

As @Jared Smith said, there was a Problem with subscribe() not receiving pubsub, so I kinda hacked something together by going to the server code and changing const pubsub to export const pubsub and I imported it into the resolvers. Seems like an unelegant solution but it does the job for now!

Assuming that you have only one cookie which is your jwt, you could get it with the socket param like so :

This seems to be a bug in the JDK: JDK-7141231

Despite java.net.SocksSocketImpl in theory supporting proxy failover; in reality this does apparently not work because after the first failed connection attempt the socket is closed, but that same closed socket is used for any subsequent connection attemps, which therefore fail with "Socket closed" (which you are seeing).

The reason why changing the proxy type to HTTP "works" is because it performs a direct connection, ignoring all other specified proxies.

You can create a route scope:

Look at the examples in the docs for Data. It seems you have to put your initialized struct in a Mutex and then add that to your App. Also beware that you need to include it in your path fn as a Mutex as well.

app.use(helmet());

is an alias for the following:

How can I connect between container?

In your current configuration you can't connect directly between containers. You would have to have Nginx connect to the internal load balancer that is connected to the Django tasks.

Web Browser -> Public Nginx Load Balancer -> Nginx Container -> Private Django Load Balancer -> Django Container.

I would suggest looking into running both containers in the same ECS task. You would probably save a good bit of money by only having one load balancer and half as many Fargate instances. The traffic flow would look like this:

Web Browser -> Public Load Balancer -> Nginx Container on port 80 -> Django Container on port 8011.

In that scenario you would configure Nginx to proxy requests to 127.0.0.1:8011. All containers in the same task can connect to each other over 127.0.0.1 inside a Fargate instance. See the Fargate networking documentation here.

A much more advanced setup would be to keep each container running as a separate task, and use AWS App Mesh for internal container communication, instead of internal load balancers. This is probably overkill for your situation, and much more appropriate in a large environment with many microservices deployed independently.

Nothing heavy, you have to change only few things. As you want to add graphql-subscription then you need to install it also beside subscriptions-transport-ws and @graphql-tools/schema that you already installed. Just install one more that is graphql-subscriptions.

You don't need to add a dependency for the http server, it is in the jdk.

Perhaps you need to require it as a module.

Asker confirmed this worked in comments:

my javafx app does have a module-info.java file and by adding requires jdk.httpserver I am able to get past the errors

The Microsoft library should define a module-info.java file which appropriately defines the module and its requirements; however, it does not do so. Log a bug report in their issue tracker. You might be able to get it to work in a modular environment by some hacks or VM arguments or running stuff off the class path instead.

Try to replicate this behavior in a modular Java app (app with module-info.java), which does not use JavaFX, to create a minimal reproducible example, then edit the question to include your example and also put the example in your issue report to Microsoft.

Asker also did this, as confirmed in comments, see the issue report at:

• https://github.com/AzureAD/microsoft-authentication-library-for-java/issues/473

The second exception you posted,