You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I propose introducing a configurable option in the Nomad configuration file in the UI section to allow users to decrease the timeout for long-lived connections. This feature would enable users to specify a shorter timeout period according to their requirements.
Use-cases
In scenarios where the Nomad UI is proxied through services like Cloudflare, which impose timeout restrictions on requests for non-enterprise customers, users face disconnection issues due to the long-lived connections in Nomad UI exceeding Cloudflare's timeout limits. By having a configurable timeout option, users can set appropriate timeout values to prevent such disconnection issues and ensure the Nomad UI remains accessible and functional.
Attempted Solutions
Currently, the only solution is either to not use cloudflare or to use their enterprise subscription.
The text was updated successfully, but these errors were encountered:
Hi @cberescu and thanks for raising this issue. It sounds like a sensible idea to me. I'll pass this over to our UI team who will be better placed to handle and assess this.
Proposal
I propose introducing a configurable option in the Nomad configuration file in the UI section to allow users to decrease the timeout for long-lived connections. This feature would enable users to specify a shorter timeout period according to their requirements.
Use-cases
In scenarios where the Nomad UI is proxied through services like Cloudflare, which impose timeout restrictions on requests for non-enterprise customers, users face disconnection issues due to the long-lived connections in Nomad UI exceeding Cloudflare's timeout limits. By having a configurable timeout option, users can set appropriate timeout values to prevent such disconnection issues and ensure the Nomad UI remains accessible and functional.
Attempted Solutions
Currently, the only solution is either to not use cloudflare or to use their enterprise subscription.
The text was updated successfully, but these errors were encountered: