forked from docker-flow/docker-flow-proxy
-
Notifications
You must be signed in to change notification settings - Fork 17
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
Feature: per-backend http-keep-alive #198
Comments
That would be great. |
I could not find time to do it today. Since I'll be offline for a week starting this weekend, I'm afraid to make any change to the project and, potentially, cause problems while I'm not available. I'll work on this start from the week after next. |
Available in the release 1.310. Can you please try it out and let me know it went? |
It is working for me, thank you very much. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Please make
http-keep-alive
configurable per backend, not only globally.For example, if there's already
CONNECTION_MODE=http-keep-alive
envvar to set that, makecom.df.connectionMode=http-keep-alive
to keep options consistent.The text was updated successfully, but these errors were encountered: