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.

Sign up for GitHub

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

Request timeouts #30

Open
1 task
aantron opened this issue Apr 12, 2021 · 0 comments
Open
1 task

Request timeouts #30

aantron opened this issue Apr 12, 2021 · 0 comments
Labels
🔒 security 🤷‍♀️ upstream

Comments

@aantron
Copy link
Owner

aantron commented Apr 12, 2021 •
edited
Loading

This requires (probably) patching http/af and h2. At the moment, it is possible to open connections and never send any data. The connections remain open. Such connections never even reach Dream, but linger in the lower-level HTTP libraries indefinitely. The timeout should probably cover the entire span from when the lower-level server first open the connection, to when it passes a request to Dream, to also catch trickling of data.

  • Ability to simply drop requests?
@aantron aantron added this to the alpha3 milestone Jul 19, 2021
@aantron aantron removed this from the alpha3 milestone Feb 13, 2022
tchibanda24 pushed a commit to tchibanda24/dream that referenced this issue Feb 5, 2025
@dinosaure
Merge pull request aantron#30 from dinosaure/refactorize
16f6e7e 
Refactorize the code on a common impl. needed to manipulate a Mirage_flow.S/Mimic.flow
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
🔒 security 🤷‍♀️ upstream
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@aantron