-
Notifications
You must be signed in to change notification settings - Fork 5k
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
v2.11.1 breaks file upload in some cases - related to PR #10569 (with solution described) #10595
Comments
Related to #10589 as well |
Seeing this too, rolled back to v2.11.0
|
I suggest that, if you're going to merge the non-upload-specific lingeringTimeout tickets into this one as duplicates, that someone updates the description of the ticket to cover all of the lingeringTimeout issues. |
I think such a feature should not be part of a patch release 😕 |
It absolutely should not be part of a patch release if semver is being followed, which it is according to https://doc.traefik.io/traefik/deprecation/releases/ |
On behalf of the maintainer team, sorry for the inconvenience. |
Welcome!
What did you do?
The issue seems to be related to #10569
We have an internal app based on SvelteKit. With traefik v2.11.0 everything works, but updating to v2.11.1 breaks the file upload.
We could get it solved by increasing the
transport.respondingTimeouts.tcp.lingeringTimeout
(see configuration below). Maybe the default of 2s is a bit too low.What did you see instead?
With traefik v2.11.1, the file upload breaks and traefik logs
level=debug msg="'499 Client Closed Request' caused by: context canceled"
What version of Traefik are you using?
What is your environment & configuration?
Entrypoint before (breaks):
Entrypoint after (works again)
Traefik runs on a default linux webserver with docker compose, similar to this example: https://github.com/wollomatic/traefik-hardened
If applicable, please paste the log output in DEBUG level
level=debug msg="'499 Client Closed Request' caused by: context canceled"
The text was updated successfully, but these errors were encountered: