Semjon Nordmann 9844df27de Support for chaning the HTTP and HTTPS port that hosts will listen on ...

I have seen a few issues that mention that changing the port that nginx
listens on is important (especially when using hostNetwork).

I am not totally convinced that NPM should allow these use-cases but I
was bored enough to implement it anyway.

Related Issue: #4122

2024-10-31 16:14:07 +01:00

..

_access.conf

Update _access.conf

2024-10-24 14:04:17 +13:00

_assets.conf

v2.1.0 (#293)

2020-02-19 15:55:06 +11:00

_certificates.conf

v2.1.0 (#293)

2020-02-19 15:55:06 +11:00

_exploits.conf

v2.1.0 (#293)

2020-02-19 15:55:06 +11:00

_forced_ssl.conf

v2.1.0 (#293)

2020-02-19 15:55:06 +11:00

_header_comment.conf

v2.1.0 (#293)

2020-02-19 15:55:06 +11:00

_hsts_map.conf

only add hsts header with https.

2023-12-02 03:26:34 +01:00

_hsts.conf

only add hsts header with https.

2023-12-02 03:26:34 +01:00

_listen.conf

Support for chaning the HTTP and HTTPS port that hosts will listen on

2024-10-31 16:14:07 +01:00

_location.conf

Cleaning unused variable.

2024-10-28 15:18:54 +03:00

dead_host.conf

only add hsts header with https.

2023-12-02 03:26:34 +01:00

default.conf

Add support for nginx 444 default response

2023-05-22 11:59:50 +10:00

ip_ranges.conf

v2.1.0 (#293)

2020-02-19 15:55:06 +11:00

letsencrypt-request.conf

All logs in single folder

2021-06-29 23:07:54 +02:00

proxy_host.conf

only add hsts header with https.

2023-12-02 03:26:34 +01:00

redirection_host.conf

only add hsts header with https.

2023-12-02 03:26:34 +01:00

stream.conf

allows hostname instead of ip for streams

2021-04-24 01:09:01 +02:00