#1814 closed enhancement (invalid)
What should I do about the warning: "upstream response is buffered to a temporary file"?
| Reported by: | Owned by: | ||
|---|---|---|---|
| Priority: | minor | Milestone: | |
| Component: | documentation | Version: | 1.16.x |
| Keywords: | Cc: | ||
| uname -a: | Linux 0cc83ae1078e 3.10.0-957.12.2.el7.x86_64 #1 SMP Tue May 14 21:24:32 UTC 2019 x86_64 Linux | ||
| nginx -V: | nginx version: nginx/1.16.0 | ||
Description
I'm one of those people that gets really concerned about warnings in my system's logs. I am seeing this one and not finding any reasonable advice about it.
an upstream response is buffered to a temporary file
I've read the proxy_buffering section and related directives documentation and can't really figure out...
- Why is this a warning, at all? (you support file buffering, is it bad?)
- What can I do about it? (should I increase memory buffers? the docs on proxy_buffer_size mention the size being carefully selected and only mention maybe reducing it)
- When should I disable file buffering, if at all?
I see that the warning was last changed some 15 years ago, but I can't find any relevant comments or commit messages to explain any of these questions.
---
I'm running nginx:stable-alpine in a Docker container (perhaps you have specific advice about file buffering in a container filesystem):
Change History (2)
comment:1 by , 5 years ago
| Resolution: | → invalid |
|---|---|
| Status: | new → closed |
comment:2 by , 5 years ago
OK, if I simply open a "documentation" issue saying that this should be an 'info' message, at worst, is that gonna get closed, too?
Note:
See TracTickets
for help on using tickets.
For questions, please use support options available.