gnodet-bot commented on code in PR #29056:
URL: https://github.com/apache/camel/pull/29056#discussion_r4458549856


##########
docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_22.adoc:
##########
@@ -29,6 +29,16 @@ The text of a body part now ends exactly where the boundary 
delimiter begins: th
 line is removed as the sender wrote it, CRLF or a bare LF. Before, two 
characters were always removed, so a part
 framed with bare line feeds (as `openssl cms -sign` writes them without 
`-crlfeol`) lost its last byte.
 
+=== camel-as2 - the asynchronous MDN allow-list matches the host and port
+
+The `asyncMdnAllowedHosts` option now matches the full authority - host and 
port - of the asynchronous MDN delivery
+address, rather than the host alone. Each entry is a host with an optional 
port in `host:port` form (IPv6 literals use
+bracket notation, for example `[::1]` or `[::1]:8443`). A bare-host entry (for 
example `partner.example`) now matches
+only the default port for the scheme (80 for `http`, 443 for `https`); to 
deliver to a non-default port, list it
+explicitly (for example `partner.example:8443`).
+
+A deployment that lists a bare host and receives asynchronous MDNs on a 
non-default port must add the port to the entry.
+

Review Comment:
   ⚠️ **Missing: `asyncMdnRequireHttps` not documented here.** The section 
describes the `asyncMdnAllowedHosts` host+port scoping change but doesn't 
mention the new `asyncMdnRequireHttps` boolean option added in this PR. 
Operators upgrading to 4.22 will encounter both options together and should 
have migration guidance for both — in particular that 
`asyncMdnRequireHttps=true` will refuse async MDN delivery to plain `http` 
addresses and that the default (`false`) preserves the prior behaviour.



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to