Re: Duplicate Content-Length header with same value, recent change in behavior intentional?

2023-04-19 Thread Maxim Dounin
Hello! On Wed, Apr 19, 2023 at 08:57:28AM -0400, Jesse Stimpson via nginx wrote: > I've noticed a recent change in behavior that occurred between releases > 1.22.1 and 1.23.4, and I'm unable to find this particular change documented. > > If an upstream proxy sends a response with duplicate Conte

RE: Duplicate Content-Length header with same value, recent change in behavior intentional?

2023-04-19 Thread Thomas Ward
I don't think NGINX has any default duplicate header handing and hasn't really. My guess is that you've simply not seen this behavior in the past. You can suppress the backend header: proxy_hide_header Content-Length; Note that the behavior hasnt changed and only *certain* headers remain def

Re: Duplicate Content-Length header with same value, recent change in behavior intentional?

2023-04-19 Thread Jesse Stimpson via nginx
Yes, apologies for being unclear. Indeed, the upstream proxy is the one generating the duplicate header. My message is primarily concerning the behavior of nginx upon recognizing such a duplicate from the upstream. In order to complete my testing, I wrote an http server as my upstream that purposef

RE: Duplicate Content-Length header with same value, recent change in behavior intentional?

2023-04-19 Thread Thomas Ward
This sounds like your backend and nginx are both generating the header. NGINX hasn't changed to the point it would create two headers, but if your backend is adding the header as well as nginx then there's your problem. Sent from my Galaxy Original message From: Jesse Sti

Duplicate Content-Length header with same value, recent change in behavior intentional?

2023-04-19 Thread Jesse Stimpson via nginx
Hello, I've noticed a recent change in behavior that occurred between releases 1.22.1 and 1.23.4, and I'm unable to find this particular change documented. If an upstream proxy sends a response with duplicate Content-Length headers, both of the same value, nginx 1.22.1 allows the response to be s

Re: TLS 1.2 and TLS1.3 extensions supported by nginx

2023-04-19 Thread preetham g
If the extensive list is not available here are the specific extensions currently I'm looking for : TLS 1.2 | signed_certificate_timestamp, or sct (0x0012) | [RFC6962] | | encrypt_then_mac (0x0016) | [RFC7366] | | status_request (0x0005)

TLS 1.2 and TLS1.3 extensions supported by nginx

2023-04-19 Thread preetham g
Hi Team, I wanted the list of the TLS 1.2 and TLS 1.3 extensions that are currently being supported by the Nginx. Can you please provide the same. Regards Preetham ___ nginx mailing list nginx@nginx.org https://mailman.nginx.org/mailman/listinfo/nginx

Re: resolver does not work

2023-04-19 Thread basti
Hello Maxim, I have found. nginx query ipv4 and ipv6 as expected. systemd-resolved return servfail when there is no ipv6. I think it should return nodata. When I set ipv6=off in nginx all is fine. Best Regards, On 19.04.23 02:51, Maxim Dounin wrote: Hello! On Tue, Apr 18, 2023 at 10:25:09