feat(smart-proxy): calculate when SNI is required for TLS routing and allow session tickets for single-target passthrough routes; add tests, docs, and npm metadata updates
This commit is contained in:
10
changelog.md
10
changelog.md
@@ -1,5 +1,15 @@
|
||||
# Changelog
|
||||
|
||||
## 2026-01-30 - 22.4.0 - feat(smart-proxy)
|
||||
calculate when SNI is required for TLS routing and allow session tickets for single-target passthrough routes; add tests, docs, and npm metadata updates
|
||||
|
||||
- Add calculateSniRequirement() and isWildcardOnly() to determine when SNI is required for routing decisions
|
||||
- Use the new calculation to allow TLS session tickets for single-route passthrough or wildcard-only domains and block them when SNI is required
|
||||
- Replace previous heuristic in route-connection-handler with the new SNI-based logic
|
||||
- Add comprehensive unit tests (test/test.sni-requirement.node.ts) covering multiple SNI scenarios
|
||||
- Update readme.hints.md with Smart SNI Requirement documentation and adjust troubleshooting guidance
|
||||
- Update npmextra.json keys, add release registries and adjust tsdoc/CI metadata
|
||||
|
||||
## 2026-01-30 - 22.3.0 - feat(docs)
|
||||
update README with installation, improved feature table, expanded quick-start, ACME/email example, API options interface, and clarified licensing/trademark text
|
||||
|
||||
|
||||
Reference in New Issue
Block a user