Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Override timeout values at a route level #2195

Closed
selfcontained opened this issue Nov 20, 2014 · 2 comments
Closed

Override timeout values at a route level #2195

selfcontained opened this issue Nov 20, 2014 · 2 comments
Assignees
Labels
feature New functionality or improvement
Milestone

Comments

@selfcontained
Copy link

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.

server.route({
  ...
  config: {
    timeout: {
      server: 4500
  }
});
@hueniverse hueniverse self-assigned this Nov 23, 2014
@hueniverse hueniverse added this to the 8.0.0 milestone Nov 23, 2014
@hueniverse
Copy link
Contributor

Replaces by #2203

@Marsup Marsup added feature New functionality or improvement and removed request labels Sep 20, 2019
@lock
Copy link

lock bot commented Jan 9, 2020

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.

@lock lock bot locked as resolved and limited conversation to collaborators Jan 9, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
feature New functionality or improvement
Projects
None yet
Development

No branches or pull requests

3 participants