Increase proxy limit from 30s to 60s

[abriginets]

Bug

• Related issues linked using fixes #number
• Integration tests added
• Errors have helpful link attached, see contributing.md

Fixes #36251

Increasing the limit since original issue wasn't addressed in 4 months. 60_000 value was picked based on default nginx values. See proxy_connect_timeout, proxy_read_timeout and proxy_send_timeout.

[abriginets]

Ideally this value should be configurable to match any reverse proxy configuration. For now increasing the limit to reduce the amount of errors in people's deployments.

[ijjk]

Hi, the 30s limit here is intentional to match edge defaults like Vercel, we can add an experimental config like experimental.proxyTimeout to allow configuring this though.

[ijjk]

Hi, I'm gonna close this for now per-above, feel free to open a fresh PR with the mentioned experimental config though!

[bcheidemann]

Hi, the 30s limit here is intentional to match edge defaults like Vercel, we can add an experimental config like experimental.proxyTimeout to allow configuring this though.

@abriginets are you planning to raise a PR for this? If not then I will raise one 😁

[abriginets]

@abriginets are you planning to raise a PR for this? If not then I will raise one 😁

I'm currently busy with some other work so it would be great if you can open a PR.

[bcheidemann]

@abriginets are you planning to raise a PR for this? If not then I will raise one 😁

I'm currently busy with some other work so it would be great if you can open a PR.

Thanks for the quick confirmation on this. I will raise a PR later tonight 👍

[bcheidemann]

Hi, the 30s limit here is intentional to match edge defaults like Vercel, we can add an experimental config like experimental.proxyTimeout to allow configuring this though.

I have raised a new PR for adding an experimental config as you suggested @ijjk. See #40289