push.rocks/smartproxy
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix(route-connection-handler): Forward non-TLS connections on HttpProxy ports to fix ACME HTTP-01 challenge handling

Browse Source
This commit is contained in:
Philipp Kunz
2025-05-19 19:59:22 +00:00
parent 85bd448858
commit 42fe1e5d15
17 changed files with 1020 additions and 530 deletions
Download Patch File Download Diff File Expand all files Collapse all files

15
changelog.md
View File

@ -1,5 +1,20 @@
# Changelog
## 2025-05-19 - 19.3.9 - fix(route-connection-handler)
Forward non-TLS connections on HttpProxy ports to fix ACME HTTP-01 challenge handling
- Added a check in RouteConnectionHandler.handleForwardAction to see if the incoming connection is non-TLS and if its port is in useHttpProxy, then forward to HttpProxy.
- Non-TLS connections on explicitly configured HttpProxy ports are now correctly forwarded, ensuring ACME HTTP-01 challenges succeed.
- Updated tests in test.http-fix-unit.ts, test.http-fix-verification.ts, and test.http-port8080-forwarding.ts to verify that non-TLS connections on the configured ports are handled properly.
## 2025-05-19 - 19.3.8 - fix(route-connection-handler)
Fix HTTP-01 ACME challenges on port 80 by properly forwarding non-TLS connections to HttpProxy
- Fixed a bug where non-TLS connections on ports configured in useHttpProxy were not being forwarded to HttpProxy
- Added check for non-TLS connections on HttpProxy ports in handleForwardAction method
- This fix resolves ACME HTTP-01 challenges failing on port 80 when useHttpProxy includes port 80
- Added test/test.http-fix-unit.ts to verify the fix works correctly
## 2025-05-19 - 19.3.8 - fix(certificate-manager)
Preserve certificate manager update callback in updateRoutes