upstream filter: upstream filter couldn't handle body buffer correctly
Open
enhancement
investigate
no stalebot
- Dominant language
- C++
- Stars
- 28.9k
- Forks
- 5.6k
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 428
Description
*Title*: *upstream filter: upstream filter couldn't handle body stop iteration correctly*
The upstream filter couldn't handle the body buffer correctly. Because when the connection is ready, it will trigger a `continueDecoding()` anyway.
If this is by design, I think we should document it clearly. Or is this a bug?
Contributor guide
Assessment
This issue has not been assessed yet.