Changes with nginx 1.25.5 16 Apr 2024
*) Feature: virtual servers in the stream module.
*) Feature: the ngx_stream_pass_module.
*) Feature: the "deferred", "accept_filter", and "setfib" parameters of
the "listen" directive in the stream module.
*) Feature: cache line size detection for some architectures.
Thanks to Piotr Sikora.
*) Feature: support for Homebrew on Apple Silicon.
Thanks to Piotr Sikora.
*) Bugfix: Windows cross-compilation bugfixes and improvements.
Thanks to Piotr Sikora.
*) Bugfix: unexpected connection closure while using 0-RTT in QUIC.
Thanks to Vladimir Khomutov.
----
Roman Arutyunyan
arut at nginx.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nginx.org/pipermail/nginx/attachments/20240416/b1ccfd4f/attachment.htm>
Hi,
(Tue, 16 Apr 20:40) Roman Arutyunyan:
> Changes with nginx 1.25.5 16 Apr 2024
>
> *) Feature: virtual servers in the stream module.
>
> *) Feature: the ngx_stream_pass_module.
>
> *) Feature: the "deferred", "accept_filter", and "setfib" parameters of
> the "listen" directive in the stream module.
>
> *) Feature: cache line size detection for some architectures.
> Thanks to Piotr Sikora.
>
> *) Feature: support for Homebrew on Apple Silicon.
> Thanks to Piotr Sikora.
>
> *) Bugfix: Windows cross-compilation bugfixes and improvements.
> Thanks to Piotr Sikora.
>
> *) Bugfix: unexpected connection closure while using 0-RTT in QUIC.
> Thanks to Vladimir Khomutov.
I'm subscribed to Mercurial Atom feed also.
There are incorrect links, they contain redundant port definition,
and because of that there is an SSL error: packet length too long.
i.e. https://hg.nginx.org:80/nginx/rev/8618e4d900cc
> *) Feature: the ngx_stream_pass_module.
Hello,
what is the difference between pass from ngx_stream_pass_module and
proxy_pass from ngx_stream_proxy_module?
As in what entails "directly" in "allows passing the accepted connection
directly to any configured listening socket"?
wbr
rr
Hello,
> On 17 Apr 2024, at 6:32 PM, Reinis Rozitis via nginx <nginx at nginx.org> wrote:
>
>> *) Feature: the ngx_stream_pass_module.
>
> Hello,
> what is the difference between pass from ngx_stream_pass_module and
> proxy_pass from ngx_stream_proxy_module?
>
> As in what entails "directly" in "allows passing the accepted connection
> directly to any configured listening socket"?
In case of "pass" there's no proxying, hence zero overhead.
The connection is passed to the new listening socket like it was accepted by it.
----
Roman Arutyunyan
arut at nginx.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nginx.org/pipermail/nginx/attachments/20240417/741d311b/attachment.htm>
Hi...
On Wed, Apr 17, 2024 at 3:27 PM Roman Arutyunyan wrote:
>
> Hello,
>
> On 17 Apr 2024, at 6:32 PM, Reinis Rozitis via nginx <nginx at nginx.org> wrote:
>
> *) Feature: the ngx_stream_pass_module.
>
>
> Hello,
> what is the difference between pass from ngx_stream_pass_module and
> proxy_pass from ngx_stream_proxy_module?
>
> As in what entails "directly" in "allows passing the accepted connection
> directly to any configured listening socket"?
>
>
> In case of "pass" there's no proxying, hence zero overhead.
> The connection is passed to the new listening socket like it was accepted by it.
Please, can you spot these overheads in proxying?
Thanks.
On Fri, 19 Apr 2024 03:14:44 +0200,
Fabiano Furtado Pessoa Coelho wrote:
>
> Please, can you spot these overheads in proxying?
>
Establishing and accepting a brand new connection, writing and reading of
requests. Maybe buffering. A lot of useless context switching between
user and kernel spaces. With possibility to enjoy not enough free ports.
Shall I continue?
--
wbr, Kirill
Hello
As I understand we better replace all proxy_pass to pass when upstream
server is localhost, but pass does not work with remote upstreams.
Is that right?
Sébastien
Le ven. 19 avr. 2024 à 09:38, Kirill A. Korinsky <kirill at korins.ky> a
écrit :
> On Fri, 19 Apr 2024 03:14:44 +0200,
> Fabiano Furtado Pessoa Coelho wrote:
> >
> > Please, can you spot these overheads in proxying?
> >
>
> Establishing and accepting a brand new connection, writing and reading of
> requests. Maybe buffering. A lot of useless context switching between
> user and kernel spaces. With possibility to enjoy not enough free ports.
>
> Shall I continue?
>
> --
> wbr, Kirill
> _______________________________________________
> nginx mailing list
> nginx at nginx.org
> https://mailman.nginx.org/mailman/listinfo/nginx
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nginx.org/pipermail/nginx/attachments/20240419/fdc28110/attachment.htm>
On Fri, 19 Apr 2024 10:02:00 +0200,
Sébastien Rebecchi wrote:
>
> As I understand we better replace all proxy_pass to pass when upstream
> server is localhost, but pass does not work with remote upstreams.
> Is that right?
>
It depends on your use case I guess.
Frankly speaking I don't see any reason to use it, and do not accept
connection by target server with one exception: you need some module which
exists only for ngx_stream_...
--
wbr, Kirill