-
Notifications
You must be signed in to change notification settings - Fork 5.1k
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
traefik reset a persistence connection to upstream #7154
Comments
i write a proxy used golang ,The problem is still happen. |
Hi @ccdeville , thank you for submitting this issue. In order to investigate this further, it'd be helpful if the team had an example that can reproduce the issue. It sounds like this may be an issue with the net/http package, but if you could provide an example docker image and steps to reproduce, it'd help us better understand the issue you're encountering. |
potentially related, and may reproduce the issue on traefik -- caddyserver/caddy#3557 (comment) |
Hi @notsureifkevin thank you for your reply,I write the example in this issue -- golang/go#40747 |
Hi! I'm Træfiker 🤖 the bot in charge of tidying up the issues. I have to close this one because of its lack of activity 😞 Feel free to re-open it or join our Community Forum. |
A fix for this problem in our case (using a Kubernetes Daemon Set deployment for Traefik) was to change |
Do you want to request a feature or report a bug?
Bug
What did you do?
I deploy traefik using daemonset in k8s
Client connection traefik use http/1.1
The client sends post request with keep-alive head and the reponse exceeds 4kb
The connection is busy no idle situation
What did you see instead?
The following log appears in traefik
I captured all the traffic with tcpdump
I found this issue
GitHub Pages
Is this caused by go? How can I fix it.
Output of
traefik version
: (What version of Traefik are you using?)What is your environment & configuration (arguments, toml, provider, platform, ...)?
If applicable, please paste the log output in DEBUG level (
--log.level=DEBUG
switch)The text was updated successfully, but these errors were encountered: