0.15 - updated AsyncWebServer and AsyncTCP #4834
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Backport #4796. The major improvement here is that the updated AsyncTCP fixes some errors in the handling of unexpectedly closed connections that could cause double frees or use-after-free that result in memory corruption, particularly under sustained load. The newer AsyncWebServer is backwards compatible and will not activate the queuing feature, though it does add the "emergency 503 on low heap" logic.