OK, I have no further questions.
I really hope this case doesn't happen.
" so it won't be possible to load a module built with NGX_HTTP_GZIP defined into nginx built without NGX_HTTP_GZIP (and vice versa)"
------------------------------------------------------------------
发件人：Maxim Dounin <mdounin@mdounin.ru>
发送时间：2022年12月6日(星期二) 09:03
收件人：nginx-devel <nginx-devel@nginx.org>
主　题：Re: 回复：Fixed gzip_disable_degradation defined without NGX_HTTP_DEGRADATION (broken by 3b522d7a5b34).
Hello!
On Mon, Dec 05, 2022 at 09:39:21AM +0800, 杜叶飞(淮叶) via nginx-devel wrote:
> OK, I I have another question about this.
> 'NGX_MODULE_SIGNATURE_27' should be with NGX_HTTP_GZIP as the
> following patch ?
No.
The NGX_HTTP_GZIP macro, which affects layout of nginx public
structures, already affects the binary signature, so it won't be
possible to load a module built with NGX_HTTP_GZIP defined into
nginx built without NGX_HTTP_GZIP (and vice versa). No additional
characters in the signature are needed for NGX_HTTP_GZIP.
The NGX_MODULE_SIGNATURE_27 macro is basically a spare one after
3b522d7a5b34, and can be reused for something else (or removed if
we'll decide to clean up things).
--
Maxim Dounin
http://mdounin.ru/
_______________________________________________
nginx-devel mailing list -- nginx-devel@nginx.org
To unsubscribe send an email to nginx-devel-leave@nginx.org
_______________________________________________
nginx-devel mailing list -- nginx-devel@nginx.org
To unsubscribe send an email to nginx-devel-leave@nginx.org