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

Jump to bottom

HTTP/2 proxy tunnel, fix ingress handling to stop too early #10952

Closed
wants to merge 1 commit into from
Closed

HTTP/2 proxy tunnel, fix ingress handling to stop too early #10952

wants to merge 1 commit into from

Conversation

icing
Copy link
Contributor

@icing icing commented Apr 13, 2023

  • progress ingress stopped too early, causing data from the underlying filters to not be processed and report that no tunnel data was available
  • this lead to "hangers" where no socket activity was seen but data rested in buffers

@icing
Fix processing ingress to stop too early
fbd8572 
- progress ingress stopped too early, causing data
  from the underlying filters to not be processed and
  report that no tunnel data was available
- this lead to "hangers" where no socket activity was
  seen but data rested in buffers
@bagder
Copy link
Member

bagder commented Apr 13, 2023

Thanks!

@bagder bagder closed this in 43d7ccd Apr 13, 2023
bch pushed a commit to bch/curl that referenced this pull request Jul 19, 2023
@icing @bch
cf-h2-proxy: fix processing ingress to stop too early
1c4b65a 
- progress ingress stopped too early, causing data
  from the underlying filters to not be processed and
  report that no tunnel data was available
- this lead to "hangers" where no socket activity was
  seen but data rested in buffers

Closes curl#10952
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
connecting & proxies
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
2 participants
@icing @bagder