v11.6.9

Behavior change

WebSocket upgrades whose path contains a backslash (raw or percent-encoded as %5C) are now rejected with a 400, matching the behavior of HTTP requests since @fastify/reply-from 12.8.1. Backslashes in the query string are still forwarded.

What's Changed

• fix: reject backslashes in WebSocket destination paths by @mcollina in #497

Full Changelog: v11.6.8...v11.6.9