-
Notifications
You must be signed in to change notification settings - Fork 29.7k
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
Doc describes HTTP "abort" event, but not "aborted" #6925
Comments
@nodejs/http Edit: Although I suspect there is little we can do about it at this stage? (Besides docs) |
AFAIK, they are distinct events. The I believe they were named differently because they have different meanings, and the The current documentation for |
@dougwilson: For the record, my cold read of #945 and the tests matches your summary of |
@kemitchell I think we'd accept a PR to document it. :) |
TL;DR: HTTP doc mentions
'abort'
event, but not'aborted'
. The API emits both. Doc fix?Current doc describes an
'abort'
event on HTTP streams here. That doc was added in 2ca22aa, which closed #945. #945 seems to deal with the case where.abort()
is called on a client only. It refers to nodejs/node-v0.x-archive#9278. As far as I can tell, current doc never mentions an'aborted'
event.The HTTP client emits
'abort'
from requests here.The HTTP client also emits
'aborted'
from the corresponding response (req.res
) here.The HTTP server emits
'aborted'
from requests here.'aborted'
events make it to user space. raw-body, a dep of the popular body-parser, listens for it here.A few questions:
aborted
intentionally undocumented? I see it mentioned in the CHANGELOG archives a couple of times from the 0.4.x days, here and originally (on Agent) here. Would the team welcome a doc patch mentioning it?abort
andaborted
intentionally distinct events?_Be Warned! I believe this is my first issue on Node. I've read CONTRIBUTING and friends and done my best._
Thanks to the team!
The text was updated successfully, but these errors were encountered: