fix(classes.portproxy.ts): Simplify timeout management in PortProxy and fix chained proxy certificate refresh issues
This commit is contained in:
21
changelog.md
21
changelog.md
@ -1,5 +1,26 @@
|
||||
# Changelog
|
||||
|
||||
## 2025-03-10 - 3.30.3 - fix(classes.portproxy.ts)
|
||||
Simplify timeout management in PortProxy and fix chained proxy certificate refresh issues
|
||||
|
||||
- Reduced TLS keep-alive timeout from 8 hours to 30 minutes to ensure frequent certificate refresh
|
||||
- Added aggressive TLS state refresh after 20 minutes of inactivity and secondary verification checks
|
||||
- Lowered long-lived TLS connection lifetime from 12 hours to 45 minutes to prevent stale certificates
|
||||
- Removed configurable timeout settings from the public API in favor of hardcoded sensible defaults
|
||||
- Simplified internal timeout management to reduce code complexity and improve certificate handling in chained proxies
|
||||
|
||||
## 2025-03-10 - 3.31.0 - fix(classes.portproxy.ts)
|
||||
Simplified timeout management and fixed certificate issues in chained proxy scenarios
|
||||
|
||||
- Dramatically reduced TLS keep-alive timeout from 8 hours to 30 minutes to ensure fresh certificates
|
||||
- Added aggressive certificate refresh after 20 minutes of inactivity (down from 4 hours)
|
||||
- Added secondary verification checks for TLS refresh operations
|
||||
- Reduced long-lived TLS connection lifetime from 12 hours to 45 minutes
|
||||
- Removed configurable timeouts completely from the public API in favor of hardcoded sensible defaults
|
||||
- Simplified interface by removing no-longer-configurable settings while maintaining internal compatibility
|
||||
- Reduced overall code complexity by eliminating complex timeout management
|
||||
- Fixed chained proxy certificate issues by ensuring more frequent certificate refreshes in all deployment scenarios
|
||||
|
||||
## 2025-03-10 - 3.30.2 - fix(classes.portproxy.ts)
|
||||
Adjust TLS keep-alive timeout to refresh certificate context.
|
||||
|
||||
|
Reference in New Issue
Block a user