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
Not an issue, but a feature request. It would be convenient to be able to specify/override timeout values that you can currently set at the server level (timeout.server and timeout.client) when registering a route. We've run into cases where a specific route needs more time for slow upstream dependencies, but we'd rather not increase the timeout across the whole server. Maybe setting it in the config.timeout property in the route options.
This thread has been automatically locked due to inactivity. Please open a new issue for related bugs or questions following the new issue template instructions.
lockbot
locked as resolved and limited conversation to collaborators
Jan 9, 2020
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Not an issue, but a feature request. It would be convenient to be able to specify/override timeout values that you can currently set at the server level (
timeout.server
andtimeout.client
) when registering a route. We've run into cases where a specific route needs more time for slow upstream dependencies, but we'd rather not increase the timeout across the whole server. Maybe setting it in theconfig.timeout
property in the route options.The text was updated successfully, but these errors were encountered: