oscerd opened a new pull request, #25414:
URL: https://github.com/apache/camel/pull/25414

   ## Description
   
   The 4.14, 4.18 and 4.21 upgrade guides each describe CAMEL-23588 as making 
`UndertowHeaderFilterStrategy` filter the legacy `websocket.*` Exchange-header 
prefix at the undertow transport boundary, and present that behaviour as 
shipped in 4.14.8, 4.18.3 and 4.21.0 respectively.
   
   It was not. `UndertowEndpoint` defaulted its `headerFilterStrategy` to the 
base `HttpHeaderFilterStrategy` and pushed that into the `UndertowHttpBinding` 
it creates lazily, overwriting the `UndertowHeaderFilterStrategy` the binding 
installs in its own constructor. On endpoint-configured routes the 
undertow-specific filtering never executed. CAMEL-24360 (#25367) fixed the 
wiring in 4.14.9 / 4.18.4 / 4.22.0.
   
   ## Why this matters
   
   | Guide | Currently claims | Actually took effect |
   |---|---|---|
   | `4_14` | active in 4.14.8 | 4.14.9 |
   | `4_18` | active in 4.18.3 | 4.18.4 |
   | `4_21` | active in 4.21.0 | 4.22.0 |
   
   The 4.14, 4.18 and 4.22 guides already carry the `camel-undertow - 
UndertowHeaderFilterStrategy is now the endpoint default` entry from the 
CAMEL-24360 doc-sync, so a careful reader there could piece it together. **The 
4.21 guide had no correction at all** — someone running 4.21.0 and reading that 
guide would believe `websocket.*` was being filtered at the undertow boundary 
when it never was.
   
   ## Changes
   
   A `[NOTE]` admonition at the top of each of the three sections, naming the 
mechanism and pointing at the entry that fixes it (in-file for 4.14 / 4.18, 
forward to the 4.22 guide for 4.21). All three referenced anchors were verified 
to resolve.
   
   Documentation only, no behaviour change.
   
   ## Testing
   
   Full reactor build from root (`mvn clean install -DskipTests`) green, no 
regenerated-artifact drift.
   
   ---
   _Claude Code on behalf of oscerd_


-- 
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