summaryrefslogtreecommitdiffhomepage
path: root/src/nxt_thread_cond.c
diff options
context:
space:
mode:
authorAndrew Clayton <a.clayton@nginx.com>2022-12-06 12:56:03 +0000
committerAndrew Clayton <a.clayton@nginx.com>2022-12-13 13:36:30 +0000
commitf88371ff1d5173da44b8bf152e1b261e444a6eac (patch)
tree0fea9e9424781d24992b03a26edcedfb1310c786 /src/nxt_thread_cond.c
parentdad7ef9a12f2cf16f2be011f167fc19b011ffe03 (diff)
downloadunit-f88371ff1d5173da44b8bf152e1b261e444a6eac.tar.gz
unit-f88371ff1d5173da44b8bf152e1b261e444a6eac.tar.bz2
Configuration: made large_header_buffers a valid setting.
This is an extension to the previous commit, which made large_header_buffer_size a valid configuration setting. This commit makes a related value, large_header_buffers, a valid configuration setting. While large_header_buffer_size effectively limits the maximum size of any single header (although unit will try to pack multiple headers into a buffer if they wholly fit). large_header_buffers limits how many of these 'large' buffers are available. It makes sense to also allow this to be user set. large_header_buffers is already set by the configuration system in nxt_router.c it just isn't set as a valid config option in nxt_conf_validation.c With this change users can set this option in their config if required by the following "settings": { "http": { "large_header_buffers": 8 } }, It retains its default value of 4 if this is not set. NOTE: This is being released as undocumented and subject to change as it exposes internal workings of unit. Signed-off-by: Andrew Clayton <a.clayton@nginx.com>
Diffstat (limited to 'src/nxt_thread_cond.c')
0 files changed, 0 insertions, 0 deletions