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

delayed response read #11

Closed
Tracked by #3
gr2m opened this issue Dec 22, 2021 · 1 comment · Fixed by #14
Closed
Tracked by #3

delayed response read #11

gr2m opened this issue Dec 22, 2021 · 1 comment · Fixed by #14
Labels
released

Comments

@gr2m
Copy link
Owner

gr2m commented Dec 22, 2021 •
edited
Loading

Related to missing output, I have a sense hooking into data immediately will cause some applications to miss parts of the content body. Those that don't start reading the response right after response and instead expect the stream to be paused for a while. Perhaps they're passing the response first to an async function, but by that time, the recording logic will have already unpaused the stream.
—moll/node-mitm#76 (comment)
This was referenced Dec 22, 2021
Closed
Merged
@gr2m gr2m closed this as completed in #14 Dec 22, 2021
@github-actions
Copy link

🎉 This issue has been resolved in version 1.1.3 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
released
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

fix: delayed response read gr2m/node-http-recorder
1 participant
@gr2m