On Tue, Nov 07, 2017 at 06:04:26PM +0330, Mohammad Puyandeh via nginx wrote:
Hi there,
> >>If you add "--limit-rate 16000" to that curl command, do you see output
> >>from your back-end server immediately, or only after enough time has
> >>passed that your client has sent all of the content to ng
>>If you add "--limit-rate 16000" to that curl command, do you see output
>>from your back-end server immediately, or only after enough time has
>>passed that your client has sent all of the content to nginx?
It's after, so Nginx buffers correctly here and I was mistaken
but now the question is,
On Mon, Nov 06, 2017 at 07:13:53PM +0330, Mohammad Puyandeh via nginx wrote:
Hi there,
> >>If you report that nginx starts to send the content to the back-end
> >>before nginx has received all of the content from the client, then
> >>proxy_request_buffering is not working as intended.
> Yes, tha
If you report that nginx starts to send the content to the back-end
before nginx has received all of the content from the client, then
proxy_request_buffering is not working as intended.
Yes, that's what I am reporting, I put together a very simple tornado
(python) script, I used both tcp connect
On Mon, Nov 06, 2017 at 04:23:06PM +0330, Mohammad Puyandeh via nginx wrote:
Hi there,
> If I try to upload a 200M file using POST method, nginx will pass
> chunks to back-end in less than 3 meg chunks
proxy_request_buffering says nothing about chunks being sent to the
back-end.
> a quote about
If I try to upload a 200M file using POST method, nginx will pass chunks
to back-end in less than 3 meg chunks
sample nginx config:
worker_processes auto;
user nginx;
events {
}
http {
upstream servers {
server 127.0.0.1:;
}
server {
listen 80;
c
