Proxy buffering will crash on big downloads above 1024M about docker-swag

[github-actions]

Thanks for opening your first issue here! Be sure to follow the bug or feature issue templates!

[aptalca]

All those confs are user customizable. Feel free to edit them as you see fit. We provide sample/default confs that work for most common scenarios out of the box, but other folks may have different needs.

[BrightCandle]

All I am suggesting is a more universal default given the likely use scenarios of swag. One of the big consequences of the existing setting beyond the fact it crashes in this weird way is that a local process that is proxied (to give it SSL) will be completely read as fast as possible and then the buffer is transferred to the client over time. On anything more than 8x 32KB this results in a file write onto the drive and a corresponding spike in CPU and drive usage as it copies from one process to the other as quick as the CPU will allow.

I don't think that this is the right default behaviour so if you can change it without breaking peoples installations I would suggest doing so. I have fixed it for our installation but it was a surprising problem to say the least and one setting change would improve the resource utilisation of swag quite noticeably as well as being less surprising for other users.

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[drizuid]

this is a request specific to a particular user and not the best course of action for the majority. closing this as the OP can do this themselves for this edge case.