nginx 1.19.3主线版发布,修复bug及改进功能

释放双眼,带上耳机,听听看~!
nginx 1.19.3主线版于2020年9月29日发布,修复bug及改进功能

更新内容

Feature:ngx_stream_set_module

Feature:“proxy_cookie_flags” 指令

Bugfix:如果后端返回状态码为 500、502、503、504、403、404 或 429,则会错误地应用 “stale-if-error” 缓存控制扩展

Bugfix:如果使用了缓存,并且后端返回了带有 “Vary” 标题行的响应,“[crit] cache file ... has too long header” (缓存文件...标头太长)信息可能会出现在日志中

Workaround:使用 OpenSSL 1.1.1 时,日志中可能会出现 “[crit] SSL_write() failed” 信息

Bugfix:“SSL_shutdown() failed (SSL: ... bad write retry)” 信息可能会出现在日志中; 该错误已在 1.19.2 中出现

Bugfix:如果使用 “error_page” 指令将代码 400 的错误重定向到代理位置,则在使用 HTTP/2 时,工作进程中可能会出现 segment fault

Bugfix:在 njs 模块中使用 HTTP/2 和子请求时发生套接字泄漏

原文

Changes with nginx 1.19.3                                        29 Sep 2020

    *) Feature: the ngx_stream_set_module.

    *) Feature: the "proxy_cookie_flags" directive.

    *) Feature: the "userid_flags" directive.

    *) Bugfix: the "stale-if-error" cache control extension was erroneously
       applied if backend returned a response with status code 500, 502,
       503, 504, 403, 404, or 429.

    *) Bugfix: "[crit] cache file ... has too long header" messages might
       appear in logs if caching was used and the backend returned responses
       with the "Vary" header line.

    *) Workaround: "[crit] SSL_write() failed" messages might appear in logs
       when using OpenSSL 1.1.1.

    *) Bugfix: "SSL_shutdown() failed (SSL: ... bad write retry)" messages
       might appear in logs; the bug had appeared in 1.19.2.

    *) Bugfix: a segmentation fault might occur in a worker process when
       using HTTP/2 if errors with code 400 were redirected to a proxied
       location using the "error_page" directive.

    *) Bugfix: socket leak when using HTTP/2 and subrequests in the njs
       module.

下载地址 | 更新说明

有关 nginx 版本分支的介绍请点此查看

人已赞赏
科技前沿

Android 11 正式发布 | 开发者们的舞台已就绪

2020-9-9 21:47:07

干货

个人无需营业执照开通支付宝当面付商家收款码/支持信用卡花呗/网页支付接口

2019-12-24 17:15:45

0 条回复 A文章作者 M管理员
    暂无讨论,说说你的看法吧
个人中心
购物车
优惠劵
今日签到
有新私信 私信列表
搜索