-
Notifications
You must be signed in to change notification settings - Fork 54
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
Adjusting the request timeout values #78
Comments
Is there a workaround for this? We're getting gateway timeouts fairly frequently, I'd like to know of the correct way to increase the timeout value |
@trauts2 , added timeouts env variables to control responding and forwarding timeouts at deployment time. Take a look at README.md file Included at release |
Thanks!
How can I update to this version in my Rancher 1.14 instance? I see the
previous version but not this one.
https://screencast.com/t/pNxyKwKOd7og
…On Tue, Mar 20, 2018 at 12:00 PM, Raúl Sánchez ***@***.***> wrote:
@trauts2 <https://github.com/trauts2> , added timeouts env variables to
control responding and forwarding timeouts at deployment time. Take a look
at README.md file
https://docs.traefik.io/configuration/commons/#timeouts
Included at release rawmind/alpine-traefik:1.5.4-1
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#78 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AD0TaLMJnz1o2PE9mWq1Su5lLcTthEXPks5tgTWngaJpZM4R3UzN>
.
|
I just tested this, and was able to set each of these timeout values. In my test I set them all to 180seconds, then issued a request that would take about that long. I received the timeout at 60 seconds exactly. Is it possible these values aren't making their way to traefik correctly? |
This PR describes a feature we would like to use:
traefik/traefik#1873
We have one admin task which takes several minutes to complete, and traefik is timing out. Is it possible to access this configuration without an enhancement to alpine-traefik?
Thanks!
Stu
The text was updated successfully, but these errors were encountered: