Bug 435. Login redirects and running under different hostnames

[MytsV]

Seemingly fix #435

I tested the changes by using a different hostname for referring to the local deployment. I managed to turn

into

It works for all the use cases of middleware redirects. I believe that might be the fix for the issue.

[MytsV]

This change refers to making deployments more flexible and accessible through any hostname. All the places where the hostname was specified through an environmental variable are reviewed.

[MytsV]

Regarding the second change, I made sure every feature still works locally for me

[maany]

@MytsV, the root cause of our client side routing troubles is the cache of the NextJS client side router.

Setting window.location.href to redirect to a new page forces the page to completely reload thereby opting out of the client side router of NextJS, and also resetting its cache.

There are certain performance and security nuances with the NextJS router that would be nice for us to leverage. In Next14 and 15, the staleTime is controllable and 0, respectively out of the box. I'd probably give the client side router another shot before completely changing how we do client side routing. :)

If everything fails with the framework, your solution is definitely a fix :)