echo-server | HTTP server that echos the request/response headers | REST library

I finally found the solution! Its on server block configuration all along. I moved this code to the upper of my server bracket tag, then it just works!

Do I miss anything in my current, vanilla config?

You probably exposed your echo-server app using service type - ClusterIP or NodePort which is fine if you only need to access your app locally in the cluster (ClusterIP) or using your node IP address (NodePort).

Do I need the AWS ALB or nginx ingress controller?

They both are different things, but they have similar common goal - to make your websocket app available externally and distribute traffic based on defined L7 routing routes. It's good solution if you have multiple deployments. So you need to answer yourself if you need some kind of Ingress Controller. If you are planning to deploy your application into production you should consider using those solutions, but probably it may be fine with service type LoadBalancer.

EDIT:

If you are already using service type LoadBalancer your app is already available externally. Ingress controller provides additional configuration possibilities to configure L7 traffic route to your cluster (Ingress Controllers are often using LoadBalancer under the hood). Check this answer for more details about differences between LoadBalancer and Ingress.

Also check:

• Choosing the Right Load Balancer on Amazon: AWS Application Load Balancer vs. NGINX Plus
• Configuring Kubernetes Ingress on AWS? Don’t Make These Mistakes
• WebSocket - Deploy to Kubernetes
• LoadBalancer vs Ingress

Emissary and Edge Stack actually handle TLS identically – given that curl works, I'm inclined to think that what you're seeing here is that you're following the directions to get a self-signed TLS certificate, and Postman is simply being stricter about certificates than curl is.

If you drop the -k from curl, I would expect it to fail too. Likewise, if you're doing HTTPS from a browser, most browsers are very picky about proper certificates. So I'd recommend that you start by getting a properly-signed certificate (perhaps from Let's Encrypt?), and try that.

Yes this is legal as per the JSON spec: JSON: why are forward slashes escaped?

And the Java libraries we use does that.

Does your server have a problem ? If so - then you have a bug that Karate surfaced.

And if you really want to have full control over the request, please use text but IMO it may be a waste of time: https://stackoverflow.com/a/68344856/143475

As @Peter Wood pointed out the documentation does contain the answer to my question:

Changed in version 3.2: Support for the context manager protocol was added. Exiting the context manager is equivalent to calling close().

Furthermore:

Sockets are automatically closed when they are garbage-collected, but it is recommended to close() them explicitly, or to use a with statement around them.

Since calling fileObject.close() on a fileObject that has already been closed does not produce an error commenting that specific line out did not lead to any different results.

The way I interpret that:

It is not intended to explicitly call socket.shutdown() on a socket within a with statement.

Calling socket.close() on a socket in a with statement is unnecessary.

Along with the other EchoServerHandler, I have two ChannelHandler now, I'd like to print a message from each ChannelHandler, and write back a message to Client from each ChannelHandler.

EchoServerHandler will also write msg. This will cause msg be released twice in ChannelOutboundBuffer.

You can remove EchoServerHandler or call in.retain() before write in your AnotherEchoServerHandler

Your frontend code and event code is correct. As you can see the user id being authenticated and the even is being broadcasted.

However, the event is not broadcasted to the same channel add the user authenticated to, so the user will never receive it. Somewhere in your backed code, your channel is being prefixed with messer_database.

You should check your redis and broadcast configuration and either remove the prefix or make the broadcast understand the prefix.

For anyone who needs help with this problem, my above echo reconnection code seems to be pretty stable, along with a keepAlive function to determine the state of the HTTP connection. I am still a bit uncertain of the origin of the console errors I am seeing, but I suspect they have to do with connection loss during a sleep cycle, which is not something I am particularly worried about.

I'd still be interested in hearing other thoughts if anyone has any. I am somewhat inclined to believe long-term stability of an echo connection is possible, though it does appear you have to proactively monitor it with what tools you have available.

Laravel Mix 6 removes a number of options from the CLI. You will need to update the scripts section of your package.json file accordingly.

See Update Your NPM Scripts
https://laravel-mix.com/docs/6.0/upgrade#update-your-npm-scripts

Before: