unsubscribe

On Thu, Feb 20, 2025 at 7:18 PM wrote: > > details: > https://github.com/nginx/njs/commit/89634204c4b12f17bbec826768d0d4e9dc5fae6c > branches: master > commit:89634204c4b12f17bbec826768d0d4e9dc5fae6c > user: Dmitry Volyntsev > date: Tue, 18 Feb 2025 22:53:54 -0800 > description:

Re: [nginx] SSL: ssl_buffer_size directive.

Awesome, really glad to see this! A couple of followup questions... (a) Is there any way to force a packet flush on record end? At the moment nginx will fragment multiple records across packet boundaries, which is suboptimal as it means that I need a minimum of two packets to decode any record - e

Re: [nginx] SSL: ssl_buffer_size directive.

(waking up from post-holiday coma :-)) ... Happy 2014! On Fri, Dec 20, 2013 at 12:49 PM, Alex wrote: > > This would require a bit more work than the current patch, but I'd love > to see a similar strategy in nginx. Hardcoding a fixed record size will > inevitably lead to suboptimal delivery of e

Re: [RFC] event/openssl: Add dynamic record size support for serving ssl trafic

just 3 packets? I'd suggest emitting the first CWND's worth.. aka, 10. ig [1] https://issues.apache.org/jira/browse/TS-2503 On Tue, May 12, 2015 at 7:52 AM, Ilya Grigorik wrote: > Awesome, thanks for putting this together! > > On Tue, May 5, 2015 at 6:39 AM, chen wrote: &g

Re: [RFC] event/openssl: Add dynamic record size support for serving ssl trafic

On Tue, May 12, 2015 at 7:28 PM, chen wrote: > 3) there are some old linux box that are still using IW4, We shouldn't penalize modern systems because there are some laggards. IW10 has been default setting in Linux since 2.6.38... That said, can we expose this as a configuration option? ig

Re: Re: [RFC] event/openssl: Add dynamic record size support for serving ssl trafic

On Wed, May 13, 2015 at 1:27 AM, chen wrote: > And by the way, did you think it is necessary to add bio_flush call after > each ssl_write? Good question, not sure. Perhaps someone else on the list can chime in.. ig ___ nginx-devel mailing list nginx-

[PATCH] Gzip: use zlib to write header and trailer

When nginx is used with zlib patched with [1], which provides integration with the future IBM Z hardware deflate acceleration, it ends up computing CRC32 twice: one time in hardware, which always does this, and one time in software by explicitly calling crc32(). crc32() calls were added in commits

[PATCH v2] Gzip: use zlib to write header and trailer

# HG changeset patch # User Ilya Leoshkevich # Date 1562928188 -7200 # Fri Jul 12 12:43:08 2019 +0200 # Node ID 0a056523895149d727a703242f2e2b579cfec9da # Parent 97ce2512373d7278f765f587d4cf087065a55e7c Gzip: use zlib to write header and trailer When nginx is used with zlib patched with [1

[PATCH] ssl: SSL_get0_verified_chain is available for LibreSSL >= 3.3.6

# HG changeset patch # User Ilya Shipitsin # Date 1700769135 -3600 # Thu Nov 23 20:52:15 2023 +0100 # Node ID 2001e73ce136d5bfc9bde27d338865b14b8ad436 # Parent 7ec761f0365f418511e30b82e9adf80bc56681df ssl: SSL_get0_verified_chain is available for LibreSSL >= 3.3.6 diff -r 7ec761f0365f