Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Close connection when a SSL/TLS handshake or badly formatted request header is detected #175

Merged
merged 1 commit into from
Dec 17, 2024

Conversation

mathieucarbou
Copy link
Owner

No description provided.

@mathieucarbou mathieucarbou self-assigned this Dec 17, 2024
@mathieucarbou mathieucarbou force-pushed the feat-172 branch 4 times, most recently from ece9b19 to 1a7d25d Compare December 17, 2024 13:03
@mathieucarbou
Copy link
Owner Author

@vortigont : I run all the tests and perf tests, tested with https://192.168.4.1:80/ also, connection closed,, works fine.

I will merge once the build pass and release.

@mathieucarbou mathieucarbou merged commit 5ce7df0 into main Dec 17, 2024
44 checks passed
@mathieucarbou mathieucarbou deleted the feat-172 branch December 17, 2024 13:18
@BeaverUI
Copy link

This patch has a memory leak. Every time you F5 the HTTPS request, a bit of free heap is lost.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[BUG] Memory leak (lwip layer ?) when hit with SSL request (https://ip:80)
3 participants