As the primary Foundry frontend is a web application, users are recommended to use supported browsers for optimal operation.
However, in rare cases, users with unusual networking set-ups may experience issues, despite using a supported browser.
In order to aid debugging, this page documents some of the assumptions that Foundry makes about the client endpoint's network set-up.
WebSocket Support
Many in-platform applications use WebSockets ↗ for communication between the client and the server,
and Foundry assumes that WebSocket connections are possible.
Some proxy servers require special configuration or a software upgrade in order to support WebSocket connections.
If users connect to Foundry via a proxy that does not support WebSockets, large parts of the platform may become unusable.
HTTP/2 Support
HTTP/2 support is vital for the seamless performance of the Foundry platform, as it helps facilitate the handling of a significant number of concurrent requests from Foundry applications to the backend.
Note that proxy servers can downgrade HTTP/2 connections to HTTP/1.1, which can make Foundry applications slow to the point of obstructing usability.
If you are encountering slowness when using Foundry and your connection to Foundry goes through a proxy, you should investigate the possibility that your proxy is downgrading the connection.