nocache | Middleware to disable client-side caching | Caching library

You can avoid multiple permutation by collapsing all properties in the gwt.xml which will merge all permutations into one

Finally found the solution: Changing the base docker image to: mcr.microsoft.com/windows:1809-amd64

This one contains the necessary dependencies to complete the build process. This is finally my Dockerfile (Anyways, if you know a lighter image or docker configuration to perform the build with gluonfx, please post in the comments. I will appreciate):

If you add a controller action like IsStillLoggedIn that checks if you still have a valid cookie (or whichever authentication scheme you use), perhaps you could use the visibilitychange event on the document in JavaScript - something like this:

You seem on the right track, but if you want to display a poster only on the broken link you could test if $brokenPoster is empty or not, like so:

Unconditionally calling session_start() does exactly what it says: it starts a new session without any if or then; always check for the session ID first. Also make sure, that the cookie-domain has been set up properly (this value might not match). For reference: setcookie().

Depending on the GWT version you are using, GWT will usually create several JS files. IIRC and nothing is changed, you have - using the lasting GWT version - 5 permutations. These are the files with the cryptic name that the *.nochache.js is loading.

These permutation will be loaded from the code server. And by defining files inside the Content-Security-Policy tag, you define the files which can be loaded. And because the file names always change, you have no chance to add them.

So, why not using:

It looks, you are using the response headers, not request headers. Try

Here are a few hints to help you out solving your issue.

Looking at the manifest files you shared, it's hard to tell which exact version of haproxy-ingress-controller container you are running in your cluster (btw, it's against best practices in production envs to leave it w/o tag, read more on it here).

For backend-server-naming configuration key to be working, minimum the v0.8.1 is required (it was backported).

Before you move on in troubleshooting, firstly please double check your ingress deployment for compatibility.

If I understand correctly the official documentation on this configuration key, setting a server naming of backends to pod names (backend-server-naming=pod) instead of sequences, does support a dynamic re-load of haproxy configuration, but does NOT support as of now dynamic updates to haproxy run-time configuration to server names at backend section (it was explained by haproxy-ingress author here, and here)

It means you need to restart your haproxy-ingress controller instance first, to be able to see changes in backend's server names reflected at haproxy configuration, e.g. situations when new Pod replicas appear or POD_IP changed due the Pod crash (expect addition/updates of server entries based on sequence naming).

I have tested successfully (see test below) the backend-server-naming=pod setting on v0.13.4 with classified Ingress type, based on ingressClassName field , rather than deprecated annotation kubernetes.io/ingress.class, as in your case:

I'm not claiming your configuration won't work (it should too), but it's important to know, that dynamic updates to configuration (this includes changes to backend configs) won't happen on unclassified Ingress resource or wrongly classified one, unless you're really running v0.12 or newer version.

It turns out I made a mistake when I was trying to define the 'fullURL' for my http request to fetch a token. I am new to http requests so I did not know I had made an error.

In my AgoraToken.swift file, my erroneous fullURL definition was: