reroute | highly specialised VPN fix | VPN library

I would recommend creating a custom exception type instead of reusing AccessDeniedException from Spring. In that way, you don't have to deal with the required error message at all.

@Lex Li had the right solution. I just had to remove the \ before api in the match tag.

Chris,

I haven't used linode or kong and don't know what your frontend actually does, so I'll just point out what I can see:

• The simplest dns check is to curl (or ping, dig, etc.):

  • http://[dataapi's pod ip]:80 from a host node
  • http://[kong-proxy svc's internal ip]/dataapi/api/values from a host node (or another pod - see below)

• default path matching on nginx ingress controller is pathPrefix, so your nginx ingress with path: / and nginx.ingress.kubernetes.io/rewrite-target: / actually matches everything and rewrites to /. This may not be an issue if you properly specify all your ingresses so they take priority over "/".

• you said 'using a kong ingress as a proxy to redirect incoming', just want to make sure you're proxying (not redirecting the client).

• Is chrome just relaying its upstream error from frontend-service? An external client shouldn't be able to resolve the cluster's urls (unless you've joined your local machine to the cluster's network or done some other fancy trick). By default, dns only works within the cluster.

• cluster dns generally follows [service name].[namespace name].svc.cluster.local. If dns cluster dns is working, then using curl, ping, wget, etc. from a pod in the cluster and pointing it to that svc will send it to the cluster svc ip, not an external ip.

• is your dataapi service configured to respond to /dataapi/api/values or does it not care what the uri is?

If you don't have any network policies restricting traffic within a namespace, you should be able to create a test pod in the same namespace, and curl the service dns and the pod ip's directly:

extern "C" void logLineToUart(const char * log, ...);

You need to tell it to make the name C-linker compatible the first time it is seen.

The extern "C" is only when compiling as C++. It is not legal syntax in C. You can use extern by itself (it is implied if you leave it off).

That's not very friendly... C++ accommodates sharing header files with C by accepting syntax that would not apply to C++, just to make it easy to use the same header file contents. In particular, using (void) for empty parameter lists (which is "an abomination") and allowing a comma in variadic function parameter lists ( (int x ...) is how C++ originally defined it; when the same feature got incorporated into ANSI C they used (int x, ...) with a superfluous comma that is not needed by the grammar.) C++ compilers accept both of these to make it easier to consume C headers...

But, you have to add extern "C" around everything. This introduces conditional compilation anyway, even though C++ accepts the C syntax. Note that for a single declaration, extern int foo (int); the extern is allowed and implied if you leave it out. If the C compiler allowed the linkage specification even though only "C" is available, it would make life easier. Note that in most cases, the C and C++ implementation are the same compiler suite, and often one language supports some features of the other as extensions. It would be cool if gcc etc. supported extern "C++" in C mode, since that code base certainly does know how the name encodes the parameters.

There is a lot of business logic inside the build method that blocks your UI rendering until you get the result from Firestore - this is bad and definitely not a way to go.

You should start by learning more about FutureBuilder or any state management solution on retrieving data and building the UI based on state changes. I would recommend starting from this Codelab (or any other Firestore + Flutter tutorial) just to get the idea of how to work with Firestore in Flutter: https://firebase.google.com/codelabs/firebase-get-to-know-flutter

First, it's important to note that there's no feature to make a client reconnect to the broker from which it disconnected after the client crashes/restarts. Generally speaking the client shouldn't really care about what broker it connects to; that's one of the main goals of horizontal scalability.

It's also worth noting that if the number of messages on the brokers and the number of connected clients is low enough that this condition arises frequently that almost certainly means you have too many brokers in your cluster.

That said, I believe the reason that your client isn't getting the messages it expects is because you're using the default redistribution-delay (i.e. -1) which means messages will not be redistributed to other nodes in the cluster. If you want to enable redistribution (which is seems like you do) then you should set it to >= 0, e.g.:

The URL parameters in your second link are a giveaway that your form data is being serialized as a GET request instead of submitted as a POST request.

There is no

RedirectToRoute() is used to redirect to a known route within ASP.Net. You just want to redirect to a URL so you can use Redirect($"/some/Route/on/Spa/{routeVal1}") instead.

Below I present an example of using the API IntersectionObserver which significantly helps in faster page loading. They can also be used to run movies or load page elements. I also recommend reading this article content-visibility, of course, it currently works in a few browsers only in those based on chromium, but a very interesting option that also significantly improves the speed of the page.