Opened 7 months ago

Closed 7 months ago

#1908 closed task (wontfix)

Listen Directive needs Documentation Update

Reported by: jsrz@… Owned by:
Priority: minor Milestone:
Component: documentation Version: 1.15.x
Keywords: listen directive Cc:
uname -a: Linux 1p2650v4-511 5.0.0-36-generic #39~18.04.1-Ubuntu SMP Tue Nov 12 11:09:50 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
nginx -V: nginx version: nginx/1.14.0 (Ubuntu)
built with OpenSSL 1.1.1 11 Sep 2018
TLS SNI support enabled
configure arguments: --with-cc-opt='-g -O2 -fdebug-prefix-map=/build/nginx-DUghaW/nginx-1.14.0=. -fstack-protector-strong -Wformat -Werror=format-security -fPIC -Wdate-time -D_FORTIFY_SOURCE=2' --with-ld-opt='-Wl,-Bsymbolic-functions -Wl,-z,relro -Wl,-z,now -fPIC' --prefix=/usr/share/nginx --conf-path=/etc/nginx/nginx.conf --http-log-path=/var/log/nginx/access.log --error-log-path=/var/log/nginx/error.log --lock-path=/var/lock/nginx.lock --pid-path=/run/nginx.pid --modules-path=/usr/lib/nginx/modules --http-client-body-temp-path=/var/lib/nginx/body --http-fastcgi-temp-path=/var/lib/nginx/fastcgi --http-proxy-temp-path=/var/lib/nginx/proxy --http-scgi-temp-path=/var/lib/nginx/scgi --http-uwsgi-temp-path=/var/lib/nginx/uwsgi --with-debug --with-pcre-jit --with-http_ssl_module --with-http_stub_status_module --with-http_realip_module --with-http_auth_request_module --with-http_v2_module --with-http_dav_module --with-http_slice_module --with-threads --with-http_addition_module --with-http_geoip_module=dynamic --with-http_gunzip_module --with-http_gzip_static_module --with-http_image_filter_module=dynamic --with-http_sub_module --with-http_xslt_module=dynamic --with-stream=dynamic --with-stream_ssl_module --with-mail=dynamic --with-mail_ssl_module

Description

Hello,

I would like to suggest that you update your listen directive documentation located here:
https://nginx.org/en/docs/http/ngx_http_core_module.html#listen

The document does not make any mention of the fact that starting in version 1.15.10, you can list ports as a range (e.g. 80-90). I only see this fact documented in the following blog:
https://www.nginx.com/blog/nginx-1-16-1-17-released/

Change History (1)

comment:1 by Maxim Dounin, 7 months ago

Resolution: wontfix
Status: newclosed

While port ranges are currently supported in http due to the same parsing code, they are not expected to be used in http. And that's the reason why this is not documented and won't be. The blog post in question mentions http incorrectly, it shouldn't.

Note: See TracTickets for help on using tickets.