Weird outdated state of ports (in webapp)

[Arjun Salyan]

There is varnish (with default settings) sitting in front of the server. It caches the content for 10 minutes, but it won’t do this if it finds a cookie. There are two ways the ports website sets a cookie - when setting the detailed port page as default or when while logging in.

Setting the detailed ports page as default functionality can be improved to better utilise caching. Currently if the user clicks on this button, cache is not served for the entire website unless the cookie somehow gets cleared, rendering the caching useless for that user.