mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-25 17:35:52 +03:00
[GH-ISSUE #468] Any tweaks for proxied Apache WebDAV? #394
Labels
No labels
awaiting feedback
bug
cannot reproduce
dns provider request
duplicate
enhancement
enhancement
enhancement
good first issue
help wanted
invalid
need more info
no certbot plugin available
product-support
pull-request
question
stale
troll
upstream issue
v2
v2
v2
v3
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/nginx-proxy-manager-NginxProxyManager#394
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @jacgl on GitHub (Jun 21, 2020).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/468
Hi,
As in the subject, I have WebDAV access on apache behind nginx-proxy-manager. The issue is when big files are sent to WebDAV server (let's say >50MB). It seems like nginx is buffering the whole file, and only then the file is sent to target. In the meantime there is no response to the client. The result is that proxy works only when I increase timeout to huge value.
I've read that this is typical for nginx when works as standalone webdav server: the file is written to temp buffer and then renamed, so in this case they suggest to have temp buffer and target dir on the same media. Is proxy working the same way?
In my case apache behind nginx is working with remote media, so the delay is really big.
I added "proxy_buffering off" to advanced, but it rather works in opposite direction, right?
So, any tweaks I can apply?
Regards, Jacek
@github-actions[bot] commented on GitHub (Mar 28, 2024):
Issue is now considered stale. If you want to keep it open, please comment 👍
@github-actions[bot] commented on GitHub (May 8, 2025):
Issue was closed due to inactivity.