Changelog for v43 and simplifying the readme

Author: mendhak

CHANGELOG.md

@@ -1,3 +1,7 @@
+## Version `43` - 2026-10-24
+* Rebuild to address [Node October security releases](https://nodejs.org/en/blog/vulnerability/october-2026-security-releases)
+* Used this opportunity to update to Node 26
+
 ## Version `42` - 2026-09-18
 * HTTP2 support added
 * The max header size is now implemented in code, due to Node's HTTP2 limitations. 

README.md

@@ -8,10 +8,10 @@ It comes with various options that can manipulate the response output, see the t
 
 ![browser](./screenshots/screenshot.png)
 
-The image is available on [Docker Hub](https://hub.docker.com/r/mendhak/http-https-echo): `mendhak/http-https-echo:42`  
-The image is available on [Github Container Registry](https://github.com/mendhak/docker-http-https-echo/pkgs/container/http-https-echo): `ghcr.io/mendhak/http-https-echo:42`
+The image is available on [Docker Hub](https://hub.docker.com/r/mendhak/http-https-echo): `mendhak/http-https-echo`  
+The image is available on [Github Container Registry](https://github.com/mendhak/docker-http-https-echo/pkgs/container/http-https-echo): `ghcr.io/mendhak/http-https-echo`
 
-Please do not use the `:latest` tag as it will break without warning, use a specific version instead.
+If you use the `:latest` tag, remember it could break without warning. Try to use a specific version instead.
 
 This image is executed as non root by default and is fully compliant with Kubernetes or Openshift deployment.
 
@@ -48,7 +48,7 @@ This image is executed as non root by default and is fully compliant with Kubern
 
 Run with Docker
 
-    docker run -p 8080:8080 -p 8443:8443 --rm -t mendhak/http-https-echo:42
+    docker run -p 8080:8080 -p 8443:8443 --rm -t mendhak/http-https-echo
 
 Or run with Docker Compose
 
@@ -65,13 +65,13 @@ You can choose a different internal port instead of 8080 and 8443 with the `HTTP
 
 In this example I'm setting http to listen on 8888, and https to listen on 9999.
 
-     docker run -e HTTP_PORT=8888 -e HTTPS_PORT=9999 -p 8080:8888 -p 8443:9999 --rm -t mendhak/http-https-echo:42
+     docker run -e HTTP_PORT=8888 -e HTTPS_PORT=9999 -p 8080:8888 -p 8443:9999 --rm -t mendhak/http-https-echo
 
 
 With docker compose, this would be:
 
     my-http-listener:
-        image: mendhak/http-https-echo:42
+        image: mendhak/http-https-echo
         environment:
             - HTTP_PORT=8888
             - HTTPS_PORT=9999
@@ -87,7 +87,7 @@ The certificates are at `/app/fullchain.pem` and `/app/testpk.pem`.
 You can use volume mounting to substitute the certificate and private key with your own.
 
     my-http-listener:
-        image: mendhak/http-https-echo:42
+        image: mendhak/http-https-echo
         ports:
             - "8080:8080"
             - "8443:8443"
@@ -102,14 +102,14 @@ You can use the environment variables `HTTPS_CERT_FILE` and `HTTPS_KEY_FILE` to
 
 By default, Express is configured to trust forwarded proxy headers from loopback, link-local, and private IP ranges. To also trust additional proxy IPs or subnets, set `ADDITIONAL_TRUSTED_PROXIES` to a single value or a comma-separated list.
 
-    docker run -e ADDITIONAL_TRUSTED_PROXIES="2001:db8::/32,203.0.113.10" -p 8080:8080 -p 8443:8443 --rm -t mendhak/http-https-echo:42
+    docker run -e ADDITIONAL_TRUSTED_PROXIES="2001:db8::/32,203.0.113.10" -p 8080:8080 -p 8443:8443 --rm -t mendhak/http-https-echo
 
 
 ## Decode JWT header
 
 If you specify the header that contains the JWT, the echo output will contain the decoded JWT.  Use the `JWT_HEADER` environment variable for this.
 
-    docker run -e JWT_HEADER=Authentication -p 8080:8080 -p 8443:8443 --rm -it mendhak/http-https-echo:42
+    docker run -e JWT_HEADER=Authentication -p 8080:8080 -p 8443:8443 --rm -it mendhak/http-https-echo
 
 
 Now make your request with `Authentication: eyJ...` header (it should also work with the `Authentication: Bearer eyJ...` schema too):
@@ -155,7 +155,7 @@ $ curl -sk --http2-prior-knowledge  http://localhost:8080/  | jq '.httpVersion'
 
 In the log output set the environment variable `DISABLE_REQUEST_LOGS` to true, to disable the specific ExpressJS request log lines. The ones like `::ffff:172.17.0.1 - - [03/Jan/2022:21:31:51 +0000] "GET /xyz HTTP/1.1" 200 423 "-" "curl/7.68.0"`.  The JSON output will still appear.
 
-    docker run --rm -e DISABLE_REQUEST_LOGS=true --name http-echo-tests -p 8080:8080 -p 8443:8443 -t mendhak/http-https-echo:42
+    docker run --rm -e DISABLE_REQUEST_LOGS=true --name http-echo-tests -p 8080:8080 -p 8443:8443 -t mendhak/http-https-echo
 
 
 ## Do not log specific path
@@ -164,12 +164,12 @@ Set the environment variable `LOG_IGNORE_PATH` to a path or a regex you would li
 This can help reduce noise from healthchecks in orchestration/infrastructure like Swarm, Kubernetes, ALBs, etc.
 
     # Ignore a single path    
-    docker run -e LOG_IGNORE_PATH=/ping -p 8080:8080 -p 8443:8443 --rm -t mendhak/http-https-echo:42
+    docker run -e LOG_IGNORE_PATH=/ping -p 8080:8080 -p 8443:8443 --rm -t mendhak/http-https-echo
     # Ignore multiple paths
-    docker run -e LOG_IGNORE_PATH="^\/ping|^\/health|^\/metrics" -p 8080:8080 -p 8443:8443 -t mendhak/http-https-echo:42
+    docker run -e LOG_IGNORE_PATH="^\/ping|^\/health|^\/metrics" -p 8080:8080 -p 8443:8443 -t mendhak/http-https-echo
     # Ignore all paths
-    docker run -e LOG_IGNORE_PATH=".*" -p 8080:8080 -p 8443:8443 -t mendhak/http-https-echo:42
-    docker run -e LOG_IGNORE_PATH="^" -p 8080:8080 -p 8443:8443 -t mendhak/http-https-echo:42
+    docker run -e LOG_IGNORE_PATH=".*" -p 8080:8080 -p 8443:8443 -t mendhak/http-https-echo
+    docker run -e LOG_IGNORE_PATH="^" -p 8080:8080 -p 8443:8443 -t mendhak/http-https-echo
 
 
 
@@ -196,15 +196,15 @@ Will contain a `json` property in the response/output.
 You can disable new lines in the log output by setting the environment variable `LOG_WITHOUT_NEWLINE`. For example,
 
 ```bash
-docker run -e LOG_WITHOUT_NEWLINE=true -p 8080:8080 -p 8443:8443 --rm -t mendhak/http-https-echo:42
+docker run -e LOG_WITHOUT_NEWLINE=true -p 8080:8080 -p 8443:8443 --rm -t mendhak/http-https-echo
 ```
 
 ## Send an empty response
 
 You can disable the JSON output in the response by setting the environment variable `ECHO_BACK_TO_CLIENT`. For example,
 
 ```bash
-docker run -e ECHO_BACK_TO_CLIENT=false -p 8080:8080 -p 8443:8443 --rm -t mendhak/http-https-echo:42
+docker run -e ECHO_BACK_TO_CLIENT=false -p 8080:8080 -p 8443:8443 --rm -t mendhak/http-https-echo
 ```
 
 ## Custom status code
@@ -285,7 +285,7 @@ You can have environment variables (that are visible to the echo server's proces
 Pass the `ECHO_INCLUDE_ENV_VARS=1` environment variable in.
 
 ```bash
-docker run -d --rm -e ECHO_INCLUDE_ENV_VARS=1 --name http-echo-tests -p 8080:8080 -p 8443:8443 -t mendhak/http-https-echo:42
+docker run -d --rm -e ECHO_INCLUDE_ENV_VARS=1 --name http-echo-tests -p 8080:8080 -p 8443:8443 -t mendhak/http-https-echo
 ```
 
 Then do a normal request via curl or browser, and you will see the `env` property in the response body.
@@ -325,7 +325,7 @@ openssl pkcs12 -export -in cert.pem -inkey testpk.pem -out certpkcs12.pfx
 By default, the headers in the response body are lowercased. To attempt to preserve the case of headers in the response body, set the environment variable `PRESERVE_HEADER_CASE` to true.
 
 ```bash
-docker run -e PRESERVE_HEADER_CASE=true -p 8080:8080 -p 8443:8443 --rm -t mendhak/http-https-echo:42
+docker run -e PRESERVE_HEADER_CASE=true -p 8080:8080 -p 8443:8443 --rm -t mendhak/http-https-echo
 ```
 
 > **Note:** This only has an effect over HTTP/1.1. HTTP/2 requires all header names be lowercase. 
@@ -336,23 +336,23 @@ To override the response body with a file, set the environment variable `OVERRID
 The file path needs to be in the `/app` directory.  
 
 ```bash
-docker run -d --rm -v ${PWD}/test.html:/app/test.html -p 8080:8080 -e OVERRIDE_RESPONSE_BODY_FILE_PATH=/test.html -t mendhak/http-https-echo:42
+docker run -d --rm -v ${PWD}/test.html:/app/test.html -p 8080:8080 -e OVERRIDE_RESPONSE_BODY_FILE_PATH=/test.html -t mendhak/http-https-echo
 ```
 
 ## Set a maximum header size
 
 You can use the `MAX_HEADER_SIZE` environment variable to set a maximum header size in bytes. The default is 1MB. 
 
 ```bash
-docker run -d --rm -e MAX_HEADER_SIZE=1000  -p 8080:8080 -p 8443:8443 -t mendhak/http-https-echo:42
+docker run -d --rm -e MAX_HEADER_SIZE=1000  -p 8080:8080 -p 8443:8443 -t mendhak/http-https-echo
 ```
 
 ## Cookies and Signed Cookies
 
 Make a request with a `Cookie` header and the response will include the cookies:
 
 ```bash
-docker run -d --rm --name http-echo-tests -p 8080:8080 -p 8443:8443 -t mendhak/http-https-echo:42
+docker run -d --rm --name http-echo-tests -p 8080:8080 -p 8443:8443 -t mendhak/http-https-echo
 ```
 
 Then make a request with a cookie header:
@@ -364,7 +364,7 @@ curl -s http://localhost:8080/ -H "Cookie: foo=bar; baz=qux"
 To enable signed cookie support, set the `COOKIE_SECRET` environment variable. Signed cookies appear in the `signedCookies` section of the response:
 
 ```bash
-docker run -d --rm -e COOKIE_SECRET=mysecretkey123 --name http-echo-tests -p 8080:8080 -p 8443:8443 -t mendhak/http-https-echo:42
+docker run -d --rm -e COOKIE_SECRET=mysecretkey123 --name http-echo-tests -p 8080:8080 -p 8443:8443 -t mendhak/http-https-echo
 ```
 
 Now you need to generate a signed cookie, and send it in the header. Here's a convenience node snippet:

docker-compose.yml

@@ -1,7 +1,7 @@
 version: '3'
 services:
     my-http-listener:
-        image: mendhak/http-https-echo:42
+        image: mendhak/http-https-echo
         environment:
             - HTTP_PORT=8888
             - HTTPS_PORT=9999