-
-
Notifications
You must be signed in to change notification settings - Fork 4.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
Potential issue with Caddy terminating HTTP Put requests when uploaded content exceeds 1MB limit #5899
Comments
If you know your way around git, could be bisect before, on, and after this commit: 58ab3a0 ? Also, is the client configured with |
I see that you're using the |
Yeah, the problem is with that commit. I configured the read limit to another large size and the problem is gone. Caddy should lift the limit once the first request is determined to be not an http request. For now, you can configure the read limit to be an arbitrary large number (it's only configurable through json though) or use v2.7.4 until a fix is found. |
@Anduin2017 Can you try build caddy with |
I have the same problem with pushing big docker images in private docker registry behind caddy. |
Hi, Caddy team.
We deployed a Nextcloud server with caddy as reverse proxy.
Our configuration is:
And we built our own caddy with script:
Today there came an incident indicating all uploads with file larger than 1M was failed in Nextcloud.
Log from Nextcloud:
All clients are failing with the same issue.
After downgrading to v2.7.4, the problem was mitigated. And uploads was successful.
So I believe this issue has no relationship with Nextcloud. Might because 2.7.5 may terminate an HTTP put request?
I tried to use caddy to reverse proxy other services, but all works fine.
I tried to disable HTTP2, and doesn't help.
The text was updated successfully, but these errors were encountered: