socket.io-file | node module for uploading file via Socket | Socket library

by rico345100 JavaScript Version: 2.0.31 License: MIT

X-Ray Key Features Code Snippets Community Discussions(3)Vulnerabilities Install Support

kandi X-RAY | socket.io-file Summary

socket.io-file is a JavaScript library typically used in Networking, Socket, Nodejs, Express.js, NPM applications. socket.io-file has no bugs, it has a Permissive License and it has low support. However socket.io-file has 2 vulnerabilities. You can install using 'npm i socket.io-file' or download it from GitHub, npm.

Socket.io-file is a node module for uploading file via Socket.io module

Support

Quality

Security

License

Reuse

Support

socket.io-file has a low active ecosystem.

It has 44 star(s) with 19 fork(s). There are 5 watchers for this library.

It had no major release in the last 12 months.

There are 8 open issues and 20 have been closed. On average issues are closed in 41 days. There are no pull requests.

It has a neutral sentiment in the developer community.

The latest version of socket.io-file is 2.0.31

Quality

socket.io-file has 0 bugs and 0 code smells.

Security

socket.io-file has 2 vulnerability issues reported (0 critical, 2 high, 0 medium, 0 low).

socket.io-file code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

socket.io-file is licensed under the MIT License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

socket.io-file releases are not available. You will need to build from source code and install.

Deployable package is available in npm.

Installation instructions are not available. Examples and code snippets are available.

Top functions reviewed by kandi - BETA

kandi has reviewed socket.io-file and discovered the below as its top functions. This is intended to give you an instant insight into socket.io-file implemented functionality, and help decide if they suit your requirements.

Initialize a new SocketFileFile .
Write the chunk to the write stream .
makedir recursively
Send an error to the upload .
Create a directory if it doesn t exist

Get all kandi verified functions for this library.

socket.io-file Key Features

No Key Features are available at this moment for socket.io-file.

socket.io-file Examples and Code Snippets

No Code Snippets are available at this moment for socket.io-file.

Community Discussions

Trending Discussions on socket.io-file

Can I use fs.readFile instead of fs.readFileSync. Can I use a socket stream instead?

Nodejs file download via client (client act as 'middleman' between server and file)

Socketi not emitting file after connection in nodejs

QUESTION

Can I use fs.readFile instead of fs.readFileSync. Can I use a socket stream instead?

Asked 2018-Apr-11 at 21:30

A Node.js example for a Google API contains this (for the server code). This is from Google's examples on GitHub, simplified for the purpose here:

...

ANSWER

Answered 2018-Apr-11 at 21:30

If you had looked at the documentation for client.longRunningRecognize(), you would have seen that request.audio could instead contain a URI to a google cloud store audio file.

Based on this approach, you could choose to stream fs.createReadStream(filename) as an upload to that location before calling the client.longRunningRecognize() with a request object using the RecognitionAudio#uri to the destination of the streamed upload instead of RecognitionAudio#content as a base64 string of the file.

That would prevent blocking the event loop like fs.readFileSync() would, and it would avoid buffering the whole file in memory like both fs.readFileSync() and fs.readFile() would.

It also appears that passing a protobuffer to RecognitionAudio#content would allow you to stream the audio data directly to the API request, though looking into that approach would require more knowledge about how this works.

Source https://stackoverflow.com/questions/49783403

QUESTION

Nodejs file download via client (client act as 'middleman' between server and file)

Asked 2018-Jan-31 at 23:04

First off, I know this seems illogical when I could just send the download URL to the server. The issue with that is that user's can access these download links and so for those who can I need to be able to download it. I can't really explain why as I am under NDA.

I am trying to download a file from a URL via the client (browser) and stream the data directly to the server where the file is saved so the client essentially acts as a "middleman" and does not require the file to be downloaded to the client's machine.

I have been experimenting with "socket.io-stream" and "socket.io-file" but i am having a few issues with both. "socket.io-stream" allows me to upload a specific file from the client to the server but the uploaded file has a size of 0kb and doesn't have any examples on Github.

"socket.io-file" has examples, which I followed and currently have it setup so I can use an input tag to select a file to upload to the server successfully.

From what I can see the "socket.io-file" upload function takes a file object as the parameter.

So I have two questions really:

Is there a plugin for JS (Browser) & NodeJs (Server) that would allow me to do this?

or
How can I create a File Object from an external url?

...

ANSWER

Answered 2017-Nov-20 at 17:56

I solved this is the end, using a chrome extension to download the file as a blob object, pass the object to the content script and then use socket.io-stream to upload it to the server.

Source https://stackoverflow.com/questions/47112148

QUESTION

Socketi not emitting file after connection in nodejs

Asked 2018-Jan-17 at 23:15

After searching the depths of SO and google, I've hit a wall. I can't for the life of me figure out how/why the socket is not catching the file I'm uploading via form, it just stops after connecting. When I check the console, I'm only seeing the form submit confirmation and then dialog click confirmation. I'm sure it's a fairly simple solution so I apologize if I'm making it more complicated than needed.

Server

...

ANSWER

Answered 2018-Jan-17 at 23:15

Resolved by placing emit function inside uploader.on('complete'...) rather than outside of the entire process.

Source https://stackoverflow.com/questions/48085615

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

CVE-2020-24807 HIGH

** UNSUPPORTED WHEN ASSIGNED ** The socket.io-file package through 2.0.31 for Node.js relies on client-side validation of file types, which allows remote attackers to execute arbitrary code by uploading an executable file via a modified JSON name field. NOTE: This vulnerability only affects products that are no longer supported by the maintainer.

https://www.npmjs.com/package/socket.io-file

https://github.com/rico345100/socket.io-file

https://github.com/advisories/GHSA-6495-8jvh-f28x

https://www.npmjs.com/advisories/1564

CVE-2020-15779 HIGH

A Path Traversal issue was discovered in the socket.io-file package through 2.0.31 for Node.js. The socket.io-file::createFile message uses path.join with ../ in the name option, and the uploadDir and rename options determine the path.

https://www.npmjs.com/advisories/1519

https://www.npmjs.com/package/socket.io-file

https://github.com/advisories/GHSA-9h4g-27m8-qjrg

https://github.com/rico345100/socket.io-file