Hello, I am looking at some NGINX logs that show that the upstream_response_time is in milliseconds(around 100-200 milliseconds) but the request_time for these requests are above 100 seconds. This happens intermittently only when the response payload is above 20 MB. Most of the times, these requests have a request_time of around 4-5 seconds for the same request payload. I see no CPU utilizationby libresco_27 - Nginx Mailing List - English
Hello, Previously we were using ssl_client_certificate directive to send files while SSL handshake which was increasing the latency with each request. After that we decided to move on to ssl_trusted_certificate directive as we didn't need to share these files anymore and according to NGINX docs, it says that this directive will not send any files to the server. But I started getting this erby libresco_27 - Nginx Mailing List - English
Can someone please help me with this query?by libresco_27 - Nginx Mailing List - English
Hello, I'm trying to configure the upstream keepalive in such a way that upstream closes connection after every request. I have set keepalive configuration for upstream like so keepalive 1; keepalive_requests 0; keepalive_timeout 0; But when the upstream returns a response, I see that it sends "Connection: keep-alive" in the response header. Ideally it should have closed theby libresco_27 - Nginx Mailing List - English
Hello, Is there some way to log the start time of a request in Nginx access log? Thanks in advance!by libresco_27 - Nginx Mailing List - English
Hello, I'm trying to get the current time and date with milliseconds precision. I'm using lua with nginx/openresty. Can someone help? Many thanks!by libresco_27 - Nginx Mailing List - English
Thank you so much for your help!by libresco_27 - Nginx Mailing List - English
Thanks for your answer! I have another query if we can actually see that keepalive is being disabled in nginx logs. Is it possible to confirm that if we run nginx in debug mode and if so, what kind of logs should I look for?by libresco_27 - Nginx Mailing List - English
Hello, Is there a way to totally disable keepalive form upstream? Right now, I have the following configuration in upstream to keep the figures to a minimum- keepalive: 1; keepalive_requests: 1; keepalive_timeout: 1s; keepalive_time: 1s Since, I can't change the keepalive directive's value to 0, is there a way I can remove this setting totally? Thanks!by libresco_27 - Nginx Mailing List - English
Hello there, I'm trying to write a simple regex for a map where only the first part of a string should match. I went through the documentation, which unfortunately didn't have much examples. Heres what I'm trying to achieve - map $string $redirct_string{ "~^abc*$" 1; } I also tried to change the regex to a simple "abc*", but it didn't work. Please let meby libresco_27 - Nginx Mailing List - English
Thanks Francis for your response. I tried the approach you suggested and it still doesn't seem to work. This is what I am doing right now :- limit_req_zone $default_client_id zone=sample_zone:50k rate=3r/m sync; map $client_id $default_client_id { ZZZZZ ""; $client_id $client_id; } When I try to hit the gateway with ZZZZ client_id, it still limits the requeby libresco_27 - Nginx Mailing List - English
Hi, I'm working on rate limiting for specific group of client ids where if the client id is equal to XYZ don't map it, thus, the zone doesn't get incremented. For ex - limit_req_zone $default_rate_client_id zone=globalClientRateLimit_zone:50k rate=10r/m sync; map $client_id $default_rate_client_id { "^(?!ZZZZZZ)$" "$1" } But this doesn't seem to work. Is thiby libresco_27 - Nginx Mailing List - English
But I'm not explicitly defining the value for proxy_busy_buffers_size to something. Right now it is set with the default valueby libresco_27 - Nginx Mailing List - English
Hi, What is the relationship between these three directives - proxy_busy_buffers_size, proxy_buffers and proxy_buffer_size? Currently, I'm only using proxy_buffer_size in my location block but whenever I set it to some higher number, for ex: 32k, it throws the following error - nginx: "proxy_busy_buffers_size" must be less than the size of all "proxy_buffers" minus one buby libresco_27 - Nginx Mailing List - English
Hello, I added 428 as an allowed http status code that can be returned from nginx. But when I access this from postman/insomnia the status code description comes out to be "unknown". eg - HTTP/1.1 428 Unknown, instead of HTTP/1.1 428 Precondition Required From my nginx gateway, I am just returning the status code and no description. And this works fine for all the other status codes.by libresco_27 - Nginx Mailing List - English