Keepalive disable vs enable Issues

Hi, To avoid some Issues I need to create new connections for POST (upload file) requests. But, If I disable keepalive under upstream I am getting the following error " 99: Cannot assign requested address) while connecting to upstream, " Is there a possibility to use idle connections for GET

how can I use keep alive idle connections for GET requests and new connections to POST requests

Hi, To avoid some Issues I need to create new connections for POST (upload file) requests. But, If I disable keepalive under upstream I am getting the following error " 99: Cannot assign requested address) while connecting to upstream, " Is there a possibility to use idle connections for

Re: How to redirect to https when using load balancer in front of nginx

> On 4 Sep 2019, at 18.32, j94305 wrote: > > In order to redirect http to https, you have to define a listener rule in > the ALB that redirects all traffic on port 80 to port 443 (of the ALB) with > the original path and query parameters. The status code should be a 301 > (permanent

Re: Errors suggesting nginx isn't started as root

Great catch, I hadn’t noticed that. Thanks Maxim! Now I need to figure out what that process is. The log suggests it gets started when I launch the service but doesn’t keep running. root@k2:/var/www# service nginx restart root@k2:/var/www# tail /var/log/nginx/error.log 2019/09/05 22:40:34

Re: Errors suggesting nginx isn't started as root

Hello! On Wed, Sep 04, 2019 at 03:59:41PM -0700, Palvelin Postmaster wrote: > This is still a big mystery to me. Upgrading to nginx 1.16.1 didn’t help. > > As far as I can understand, the nginx master process IS running with root > privileges. The error is from process 22399, and no

Some POST requests give 400 Bad Request when word 'select' is in the body

Hi all, we have seen that if you add the word 'SELECT' in some requests sometimes you get a 400 Bad Request. It is a use case where we save contents via POST to edit a item of our catalog. I suspect that nginx may interpret this request as a some kind of SQL injection. Do you know if it is a

Re: Feature Request proxy_cache_min_size and proxy_cache_max_size

I also encountered the same problem, but after 4 years, this feature has not been added to the latest version. Posted at Nginx Forum: https://forum.nginx.org/read.php?2,258604,285566#msg-285566 ___ nginx mailing list nginx@nginx.org

Re: still seeing 413 error with client_max_body_size 0

Oh, sorry. It's clear that the upstream is sending 413 errors, not the nginx himself. Should read the log more carefully. Sorry again. Posted at Nginx Forum: https://forum.nginx.org/read.php?2,285564,285565#msg-285565 ___ nginx mailing list

still seeing 413 error with client_max_body_size 0

Hello, I was getting the bunch of 413 statuses in the access log along with getting explicit error messages about client (logstash in my case, seems like it was trying to send bodies around 100 megabytes) trying to post body larger than the client_max_body_size. After I raised this setting to