Repository navigation
Docs: http.ServerResponse is missing socket and connection fields #12617
Description
Activity
@nodejs/documentation
Out of curiosity - may I ask what you're trying to do with the socket you get back here? I'm trying to think of cases where using the writableStream methods on the response isn't the right thing to use.
In my case I'm dealing with streaming server that receives one request and then streams data while the connection exists. I keep Response object to write to and I don't need Request object at all. But I still need socket for closing the connection.
- added a commit that references this issue
on Jun 19, 2017 - added 2 commits that reference this issue
on Jun 24, 2017 - added a commit that references this issue
on Jul 11, 2017 - added a commit that references this issue
on Jul 18, 2017
http.ServerResponsedocs are missingsocketandconnectionfields. Moreover, it should be mentioned that they're nulled afterend()so this won't work:resp.end(message, function(){ this.socket.destroy(); } );