Hi, I use nginx as reverse proxy to my Flask web server and have following
problem:
after I changed proxy pass to variable DELETE requests started to return 405
Method not allowed (while POST works fine)
location /client_data {
resolver 127.0.0.11 valid=60s;
resolv
It would be nice to have logs for this problem.
Please, make sure your log format includes upstream address and upstream
status ($upstream_addr and $upstream_status).
On 25.05.2018 12:27, ConnorMcLaud wrote:
Hi, I use nginx as reverse proxy to my Flask web server and have following
problem:
af
I see following bug (closed as invalid):
https://trac.nginx.org/nginx/ticket/1067
Comment from there:
Using variables in proxy_pass implies, that the URI specified is a full one
Posted at Nginx Forum:
https://forum.nginx.org/read.php?2,279953,279955#msg-279955
__
I changed my config to the following:
location /client_data {
resolver 127.0.0.11 valid=60s;
resolver_timeout 5s;
set $upstream_client_data web:5000;
proxy_pass http://$upstream_client_data$uri;
}
Now it works!
Posted at Nginx Forum
Hello!
On Fri, May 25, 2018 at 05:27:24AM -0400, ConnorMcLaud wrote:
> Hi, I use nginx as reverse proxy to my Flask web server and have following
> problem:
> after I changed proxy pass to variable DELETE requests started to return 405
> Method not allowed (while POST works fine)
>
>
>
Hi,
While client uploads content into permanent temp file ngx worker doesn't
process any requests until its finished.
Its an issue in case of large files (GBs) uploading since number of parallel
uploads are limited by number of workers.
https://www.nginx.com/blog/thread-pools-boost-performance-9
>>Quick and dirty patch below. It is expected to work fine on
>>systems with monotonic clocks available, but may need more work to
>>handle time changes on systems without monotonic clocks.
[..]
Thanks Maxim, I will build from source by incorporating the patch and give a
try. I hope real fix wil
