Here is all I found in the official docs:

[&lt;h2&gt;Client-side events for `socket.io` object:&lt;/h2&gt;](http://socket.io/docs/client-api/#manager(url:string,-opts:object))

 - `connect`. Fired upon a successful connection.&lt;br&gt;&lt;br&gt;
 - `connect_error`. Fired upon a connection error.&lt;br&gt;Parameters:
   - `Object` error object&lt;br&gt;&lt;br&gt;
 - `connect_timeout`. Fired upon a connection timeout.&lt;br&gt;&lt;br&gt;
 - `reconnect`. Fired upon a successful reconnection.&lt;br&gt;Parameters:
   - `Number` reconnection attempt number&lt;br&gt;&lt;br&gt;
 - `reconnect_attempt`. Fired upon an attempt to reconnect.&lt;br&gt;&lt;br&gt;
 - `reconnecting`. Fired upon an attempt to reconnect.&lt;br&gt;Parameters:&lt;br&gt;
   - `Number` reconnection attempt number&lt;br&gt;&lt;br&gt;
 - `reconnect_error`. Fired upon a reconnection attempt error.&lt;br&gt;Parameters:&lt;br&gt;
   - `Object` error object&lt;br&gt;&lt;br&gt;
 - `reconnect_failed`. Fired when couldn’t reconnect within `reconnectionAttempts`

[&lt;h2&gt;Client-side events for `socket` object:&lt;/h2&gt;](https://socket.io/docs/client-api/#socket-disconnect)

 - `connect`. Fired upon connecting.
 - `error`. Fired upon a connection error&lt;br&gt;Parameters:
   - `Object` error data
 - `disconnect`. Fired upon a disconnection.
 - `reconnect`. Fired upon a successful reconnection.&lt;br&gt;Parameters:
   - `Number` reconnection attempt number
 - `reconnect_attempt`. Fired upon an attempt to reconnect.
 - `reconnecting`. Fired upon an attempt to reconnect.&lt;br&gt;Parameters:
   - `Number` reconnection attempt number
 - `reconnect_error`. Fired upon a reconnection attempt error.&lt;br&gt;Parameters:
   - `Object` error object
 - `reconnect_failed`. Fired when couldn’t reconnect within `reconnectionAttempts`

[&lt;h2&gt;Server-side events:&lt;/h2&gt;](http://socket.io/docs/server-api/#namespace)

 - `connection` / `connect`. Fired upon a connection.&lt;br&gt;Parameters:&lt;br&gt;
   - `Socket` the incoming socket.

&lt;h3&gt;Edit:&lt;/h3&gt;

For the current version (`1.3.4`) the `reconnect_attempt` and `reconnecting`
 client-side events are synonyms.

as per title, my question is: Does Android provide any way to analyze/determine if a color (that will be obviously dynamic for the purpose) is light or dark?



Check if color is dark or light in Android

I have a Django application with a view that accepts a file to be uploaded. Using the Django REST framework I&#39;m subclassing APIView and implementing the post() method like this:


    class FileUpload(APIView):
        permission_classes = (IsAuthenticated,)

        def post(self, request, *args, **kwargs):
            try:
                image = request.FILES[&#39;image&#39;]
                # Image processing here.
                return Response(status=status.HTTP_201_CREATED)
            except KeyError:
                return Response(status=status.HTTP_400_BAD_REQUEST, data={&#39;detail&#39; : &#39;Expected image.&#39;})


Now I&#39;m trying to write a couple of unittests to ensure authentication is required and that an uploaded file is actually processed. 

    class TestFileUpload(APITestCase):
        def test_that_authentication_is_required(self):
            self.assertEqual(self.client.post(&#39;my_url&#39;).status_code, status.HTTP_401_UNAUTHORIZED)

        def test_file_is_accepted(self):
            self.client.force_authenticate(self.user)
            image = Image.new(&#39;RGB&#39;, (100, 100))
            tmp_file = tempfile.NamedTemporaryFile(suffix=&#39;.jpg&#39;)
            image.save(tmp_file)
            with open(tmp_file.name, &#39;rb&#39;) as data:
                response = self.client.post(&#39;my_url&#39;, {&#39;image&#39;: data}, format=&#39;multipart&#39;)
                self.assertEqual(status.HTTP_201_CREATED, response.status_code)

But this fails when the REST framework attempts to encode the request

    Traceback (most recent call last):
      File &quot;/home/vagrant/.virtualenvs/myapp/lib/python3.3/site-packages/django/utils/encoding.py&quot;, line 104, in force_text
        s = six.text_type(s, encoding, errors)
    UnicodeDecodeError: &#39;utf-8&#39; codec can&#39;t decode byte 0xff in position 118: invalid start byte

    During handling of the above exception, another exception occurred:

    Traceback (most recent call last):
      File &quot;/home/vagrant/webapp/myproject/myapp/tests.py&quot;, line 31, in test_that_jpeg_image_is_accepted
        response = self.client.post(&#39;my_url&#39;, { &#39;image&#39;: data}, format=&#39;multipart&#39;)
      File &quot;/home/vagrant/.virtualenvs/myapp/lib/python3.3/site-    packages/rest_framework/test.py&quot;, line 76, in post
        return self.generic(&#39;POST&#39;, path, data, content_type, **extra)
      File &quot;/home/vagrant/.virtualenvs/myapp/lib/python3.3/site-packages/rest_framework/compat.py&quot;, line 470, in generic
        data = force_bytes_or_smart_bytes(data, settings.DEFAULT_CHARSET)
      File &quot;/home/vagrant/.virtualenvs/myapp/lib/python3.3/site-packages/django/utils/encoding.py&quot;, line 73, in smart_text
        return force_text(s, encoding, strings_only, errors)
      File &quot;/home/vagrant/.virtualenvs/myapp/lib/python3.3/site-packages/django/utils/encoding.py&quot;, line 116, in force_text
        raise DjangoUnicodeDecodeError(s, *e.args)
    django.utils.encoding.DjangoUnicodeDecodeError: &#39;utf-8&#39; codec can&#39;t decode byte 0xff in position 118: invalid start byte. You passed in b&#39;--BoUnDaRyStRiNg\r\nContent-Disposition: form-data; name=&quot;image&quot;; filename=&quot;tmpyz2wac.jpg&quot;\r\nContent-Type: image/jpeg\r\n\r\n\xff\xd8\xff[binary data omitted]&#39; (&lt;class &#39;bytes&#39;&gt;)

How can I make the test client send the data without attempting to decode it as UTF-8?

How can I test binary file uploading with django-rest-framework&#39;s test client?

Does anyone know what **events** are built-in in **Socket.io**?  
For example: `connection`, `disconnect`, `join` etc.

List of Socket.io Events

Does anyone know what events are built-in in Socket.io? 
For example: <code>connection</code>, <code>disconnect</code>, <code>join</code> etc.

My node installation is at:

`/usr/local/bin/node`

and I&#39;ve added the shebang:

`#!/usr/local/bin/node`

to the top of the file and given my node app file the permissions 755, but when I try to run:

`&gt; ./my-app`

I get the old:

`-bash: ./my-app: No such file or directory`

What am I doing wrong?

node and shebang : help executing via command line

Following the upgrade to Express 4, and the removal of app.router, I&#39;m struggling to get middleware to execute after routes execute.

e.g. the following code correctly responds with &quot;hello&quot;, but never calls the configured middleware

    var express = require( &quot;express&quot; )();
    
    express.get( &quot;/&quot;, function( req, res ) {
    
    	res.send( &quot;hello&quot; );
    
    } );
    express.use( function( req, res, next ) {
    
    	console.log( &quot;world&quot; );
        next();
    
    } );
    
    express.listen( 8888 );

CLARIFICATION:

the following code shows &quot;before&quot; on the console, but not &quot;after&quot;:

    var express = require( &quot;express&quot; )();
    
    express.use( function( req, res, next ) {
    
    	console.log( &quot;before&quot; );
    	next();
    
    } );
    express.get( &quot;/&quot;, function( req, res ) {
    
    	res.send( &quot;hello&quot; );
    
    } );
    express.use( function( req, res, next ) {
    
    	console.log( &quot;after&quot; );
    	next();
    
    } );
    
    express.listen( 8888 );

Node Express 4 middleware after routes

After [yesterday&#39;s news of Shocker][1], it seems like apps inside a Docker container should not be run as root.  I tried to update my `Dockerfile` to create an app user however changing permissions on app files (while still root) doesn&#39;t seem to work.  I&#39;m guessing this is because some LXC permission is not being granted to the root user maybe?

Here&#39;s my Dockerfile:

    # Node.js app Docker file

    FROM dockerfile/nodejs
    MAINTAINER Thom Nichols &quot;thom@thomnichols.org&quot;

    RUN useradd -ms /bin/bash node

    ADD . /data
    # This next line doesn&#39;t seem to have any effect:
    RUN chown -R node /data 

    ENV HOME /home/node
    USER node

    RUN cd /data &amp;&amp; npm install

    EXPOSE 8888

    WORKDIR /data

    CMD [&quot;npm&quot;, &quot;start&quot;]


Pretty straightforward, but when I `ls -l` everything is still owned by root:

    [ node@ed7ae33e76e1:/data {docker-nonroot-user} ]$ ls -l /data
    total 64K
    -rw-r--r--  1 root root  383 Jun 18 20:32 Dockerfile
    -rw-r--r--  1 root root  862 Jun 18 16:23 Gruntfile.js
    -rw-r--r--  1 root root 1.2K Jun 18 15:48 README.md
    drwxr-xr-x  4 root root 4.0K May 30 14:24 assets/
    -rw-r--r--  1 root root  416 Jun  3 14:22 bower.json
    -rw-r--r--  1 root root  930 May 30 01:50 config.js
    drwxr-xr-x  4 root root 4.0K Jun 18 16:08 lib/
    drwxr-xr-x 42 root root 4.0K Jun 18 16:04 node_modules/
    -rw-r--r--  1 root root 2.0K Jun 18 16:04 package.json
    -rw-r--r--  1 root root  118 May 30 18:35 server.js
    drwxr-xr-x  3 root root 4.0K May 30 02:17 static/
    drwxr-xr-x  3 root root 4.0K Jun 18 20:13 test/
    drwxr-xr-x  3 root root 4.0K Jun  3 17:38 views/


---

[My updated dockerfile works great][2] thanks to @creak&#39;s clarification of how volumes work.  Once the initial files are `chown`ed, `npm install` is run as the non-root user.  And thanks to a `postinstall` hook, npm runs `bower install &amp;&amp; grunt assets` which takes care of the remaining install steps and avoids any need to `npm install -g` any node cli tools like bower, grunt or coffeescript.

  [1]: https://news.ycombinator.com/item?id=7909622
  [2]: https://gist.github.com/thom-nic/5e561e800cbc0f71555c

Running app inside Docker as non-root user

I am using express 4.0 and I&#39;m aware that body parser has been taken out of the express core, I am using the recommended replacement, however I am getting 

`body-parser deprecated bodyParser: use individual json/urlencoded middlewares server.js:15:12
body-parser deprecated urlencoded: explicitly specify &quot;extended: true&quot; for extended parsing node_modules/body-parser/index.js:74:29`

Where do I find this supposed middlewares? or should I not be getting this error?

    var express 	= require(&#39;express&#39;);
	var server 		= express();
	var bodyParser 	= require(&#39;body-parser&#39;);
	var mongoose 	= require(&#39;mongoose&#39;);
	var passport	= require(&#39;./config/passport&#39;);
	var routes		= require(&#39;./routes&#39;);

	mongoose.connect(&#39;mongodb://localhost/myapp&#39;, function(err) {
		if(err) throw err;
	});

	server.set(&#39;view engine&#39;, &#39;jade&#39;);
	server.set(&#39;views&#39;, __dirname + &#39;/views&#39;);

	server.use(bodyParser()); 
	server.use(passport.initialize());

	// Application Level Routes
	routes(server, passport);

	server.use(express.static(__dirname + &#39;/public&#39;));

	server.listen(3000);


bodyParser is deprecated express 4

NOTE: I have tried other solution given [here][1] but it didn&#39;t work

A newbie with NodeJs. I am trying to follow AngularJS pro and got stuck with setting up NodeJs server. According to book, I installed nodejs and then installed connect package using
npm install connect

then downloaded angularjs in folder next to nodejs folder. Then wrote server.js file to connect to server. Here is the content of the file:

        var connect = require(&#39;connect&#39;);
    connect.createServer(connect.static(&quot;../angularjs&quot;)).listen( 5000);


  When I run this server.js file using: 

    node server.js

I get following error:

     function app(req, res, next){ app.handle(req, res, next); }
     merge(app, proto);
     merge(app, EventEmitter.prototype);
     app.route = &#39;/&#39;;
     app.stack = [];
     return app;
     has no method &#39;static&#39;
       at Object.&lt;anonymous&gt; (C:\web\nodejs\server.js:2:36)
       at Module._compile (module.js:456:26)
       at Object.Module._extensions..js (module.js:474:10)
       at Module.load (module.js:356:32)
       at Function.Module._load (module.js:312:12)
       at Function.Module.runMain (module.js:497:10)
       at startup (node.js:119:16)
       at node.js:906:3
    
    
  [1]: https://stackoverflow.com/questions/23978734/node-connect-issue-object-function-createserver-has-no-method-static

Any ideas guys?
Thanks.


nodejs connect cannot find static

I am creating a class that has a series of events, one of them being `GameShuttingDown`. When this event is fired, I need to invoke the event handler. The point of this event is to notify users the game is shutting down and they need to save their data. The saves are awaitable, and events are not. So when the handler gets called, the game shuts down before the awaited handlers can complete.



    public event EventHandler&lt;EventArgs&gt; GameShuttingDown;

    public virtual async Task ShutdownGame()
    {
        await this.NotifyGameShuttingDown();

        await this.SaveWorlds();

        this.NotifyGameShutDown();
    }

    private async Task SaveWorlds()
    {
        foreach (DefaultWorld world in this.Worlds)
        {
            await this.worldService.SaveWorld(world);
        }
    }

    protected virtual void NotifyGameShuttingDown()
    {
        var handler = this.GameShuttingDown;
        if (handler == null)
        {
            return;
        }

        handler(this, new EventArgs());
    }

### Event registration

    // The game gets shut down before this completes because of the nature of how events work
    DefaultGame.GameShuttingDown += async (sender, args) =&gt; await this.repo.Save(blah);

I understand that the signature for events are `void EventName` and so making it async is basically fire and forget. My engine makes heavy use of eventing to notify 3rd party developers (and multiple internal components) that events are taking place within the engine and letting them react to them.

Is there a good route to go down to replace eventing with something asynchronous based that I can use? I&#39;m not sure if I should be using `BeginShutdownGame` and `EndShutdownGame` with callbacks, but that&#39;s a pain because then only the calling source can pass a callback, and not any 3rd party stuff that plugs in to the engine, which is what I am getting with events. If the server calls `game.ShutdownGame()`, there&#39;s no way for engine plugins and or other components within the engine to pass along their callbacks, unless I wire up some kind of registration method, keeping a collection of callbacks.

Any advice on what the preferred/recommended route to go down with this would be greatly appreciated! I have looked around and for the most part what I&#39;ve seen is using the Begin/End approach which I don&#39;t think will satisfy what I&#39;m wanting to do.

**Edit**

Another option I&#39;m considering is using a registration method, that takes an awaitable callback. I iterate over all of the callbacks, grab their Task and await with a `WhenAll`.

    private List&lt;Func&lt;Task&gt;&gt; ShutdownCallbacks = new List&lt;Func&lt;Task&gt;&gt;();

    public void RegisterShutdownCallback(Func&lt;Task&gt; callback)
    {
        this.ShutdownCallbacks.Add(callback);
    }

    public async Task Shutdown()
    {
        var callbackTasks = new List&lt;Task&gt;();
        foreach(var callback in this.ShutdownCallbacks)
        {
            callbackTasks.Add(callback());
        }

        await Task.WhenAll(callbackTasks);
    }

How do I await events in C#?

I have a React component called `&lt;SensorList /&gt;` that has many child `&lt;SensorItem /&gt;`s (another React component). I want to be able to declare an `onClick` event on each `&lt;SensorItem /&gt;` from within `&lt;SensorList /&gt;`. I have tried doing the following:

    sensorSelected: function(sensor) {
        console.log(&#39;Clicked!&#39;);
    },

    render: function() {
        var nodes = this.state.sensors.map(function(sensor) {
            return (
                &lt;SensorItem onClick={ this.sensorSelected } /&gt;
            );
        }.bind(this));

        return (
            &lt;div className=&quot;sensor-list&quot;&gt;
                { nodes }
            &lt;/div&gt;
        );
    }

Needless to say, I do not get any &quot;Clicked!&quot; coming up in my console. The React inspector in Chrome indicates that an `onClick` event is registered, with the above function body as it should be.

I conclude, therefore, that I can&#39;t register `onClick` events on the actual `&lt;SensorItem /&gt;` tags (I&#39;m not sure why this is, however). How do I go about achieving this otherwise?

React onClick event on component

I want to run a block of code in 10 seconds from an event, but I want to be able to cancel it so that if something happens before those 10 seconds, the code won&#39;t run after 10 seconds have gone by.

I&#39;ve been using this, but it&#39;s not cancellable:

    static func delay(delay:Double, closure:()-&gt;()) {
      dispatch_after(
        dispatch_time(
          DISPATCH_TIME_NOW,
          Int64(delay * Double(NSEC_PER_SEC))
        ),
        dispatch_get_main_queue(), closure
      )
    }

How can I accomplish this?

Cancel a timed event in Swift?

I&#39;m listening to a hardware event message, but I need to debounce it to avoid too many queries.

This is an hardware event that sends the machine status and I have to store it in a database for statistical purposes, and it sometimes happens that its status changes very often (flickering?). In this case I would like to store only a &quot;stable&quot; status and I want to implement it by simply waiting for 1-2s before storing the status to the database.

This is my code:

    private MachineClass connect()
    {
        try
        {
            MachineClass rpc = new MachineClass();
            rpc.RxVARxH += eventRxVARxH;
            return rpc;
        }
        catch (Exception e1)
        {
            log.Error(e1.Message);
            return null;
        }
    }
    
    private void eventRxVARxH(MachineClass Machine)
    {
        log.Debug(&quot;Event fired&quot;);
    }

I call this behaviour &quot;debounce&quot;: wait a few times to really do its job: if the same event is fired again during the debounce time, I have to dismiss the first request and start to wait the debounce time to complete the second event.

What is the best choice to manage it? Simply a one-shot timer?

To explain the &quot;debounce&quot; function please see this javascript implementation for key events:
http://benalman.com/code/projects/jquery-throttle-debounce/examples/debounce/

C# event debounce

I have a general question about javascript (jQuery) events/listeners.
Is there any limit for the number of click listener without getting performance problems?

Does adding too many event listeners affect performance?

So here is the deal: I&#39;m trying to use socket.io in an express project. After Express Js 4 was lauched, i&#39;ve updated my express-generator and now the app initial functions goes into `./bin/www` file, including those vars (www file contents: http://jsfiddle.net/avMa5/ )

    var server = app.listen(app.get(&#39;port&#39;), function() {..}

(check it by `npm install -g express-generator` and then `express myApp`

that being said, let&#39;s remember how socket.io docs ask us to fire it:

    var app = require(&#39;express&#39;).createServer();
    var io = require(&#39;socket.io&#39;)(app);

Ok but i can&#39;t do it inside app.js, like recommended. This should be done in ./bin/www in order to work. in ./bin/www this is what i can do to get it working:

    var io = require(&#39;socket.io&#39;)(server)

Ok this works, but i can&#39;t use the io var anywhere else, and i really don&#39;t want to put my socket.io functions on `www` file. 

I guess this is just basic syntax, but I can&#39;t get this to work, not even using `module.exports = server` or `server.exports = server` nor `module.exports.io = app(io)` on www file

So the question is: how can i use socket.io having this /bin/www file as starting point of my app?

Using socket.io in Express 4 and express-generator&#39;s /bin/www

How can I share a session with Socket.io 1.0 and Express 4.x? I use a Redis Store, but I believe it should not matter. I know I have to use a middleware to look at cookies and fetch session, but don&#39;t know how. I searched but could not find any working 

		var RedisStore = connectRedis(expressSession);
		var session = expressSession({
			store: new RedisStore({
				client: redisClient
			}),
			secret: mysecret,
			saveUninitialized: true,
			resave: true
		});
		app.use(session);

		io.use(function(socket, next) {
			var handshake = socket.handshake;
			if (handshake.headers.cookie) {
				var str = handshake.headers.cookie;
				next();
			} else {
				next(new Error(&#39;Missing Cookies&#39;));
			}
		});


How to share sessions with Socket.IO 1.x and Express 4.x?

[add]
So my next problem is that when i try adding a new dependence (npm install --save socket.io). The JSON file is also valid. I get this error:
Failed to parse json

    npm ERR! Unexpected string
    npm ERR! File: /Users/John/package.json
    npm ERR! Failed to parse package.json data.
    npm ERR! package.json must be actual JSON, not just JavaScript.
    npm ERR! 
    npm ERR! This is not a bug in npm.
    npm ERR! Tell the package author to fix their package.json file. JSON.parse 


So I&#39;ve been trying to figure out why this error has been returning. All of the files (HTML,JSON,JS) are inside the same folder on my desktop. I&#39;m using node.js and socket.io

This is my JS file:

    var app = require(&#39;express&#39;)();
    var http = require(&#39;http&#39;).Server(app);
    
    app.get(&#39;/&#39;, function(req, res){
      res.sendFile(&#39;index.html&#39;);
    });
    
    http.listen(3000,function(){
    	console.log(&#39;listening on : 3000&#39;);
    });

This is what is getting returned:

    MacBook-Pro:~ John$ node /Users/John/Desktop/Chatapp/index.js 
    listening on : 3000
    TypeError: path must be absolute or specify root to res.sendFile
        at ServerResponse.sendFile (/Users/John/node_modules/express/lib/response.js:389:11)
        at /Users/John/Desktop/Chatapp/index.js:5:7
        at Layer.handle [as handle_request] (/Users/John/node_modules/express/lib/router/layer.js:76:5)
        at next (/Users/John/node_modules/express/lib/router/route.js:100:13)
        at Route.dispatch (/Users/John/node_modules/express/lib/router/route.js:81:3)
        at Layer.handle [as handle_request] (/Users/John/node_modules/express/lib/router/layer.js:76:5)
        at /Users/John/node_modules/express/lib/router/index.js:234:24
        at Function.proto.process_params (/Users/John/node_modules/express/lib/router/index.js:312:12)
        at /Users/John/node_modules/express/lib/router/index.js:228:12
        at Function.match_layer (/Users/John/node_modules/express/lib/router/index.js:295:3)
    TypeError: path must be absolute or specify root to res.sendFile
        at ServerResponse.sendFile (/Users/John/node_modules/express/lib/response.js:389:11)
        at /Users/John/Desktop/Chatapp/index.js:5:7
        at Layer.handle [as handle_request] (/Users/John/node_modules/express/lib/router/layer.js:76:5)
        at next (/Users/John/node_modules/express/lib/router/route.js:100:13)
        at Route.dispatch (/Users/John/node_modules/express/lib/router/route.js:81:3)
        at Layer.handle [as handle_request] (/Users/John/node_modules/express/lib/router/layer.js:76:5)
        at /Users/John/node_modules/express/lib/router/index.js:234:24
        at Function.proto.process_params (/Users/John/node_modules/express/lib/router/index.js:312:12)
        at /Users/John/node_modules/express/lib/router/index.js:228:12
        at Function.match_layer (/Users/John/node_modules/express/lib/router/index.js:295:3)

node.js TypeError: path must be absolute or specify root to res.sendFile [failed to parse JSON]

I am using Socket.io with Express. In my project I have a login page and a home page. When I do successful login, I navigate to localhost:3000/home where I get this error:
    
    GET http://localhost:3000/socket.io/?EIO=3&amp;transport=polling&amp;t=1418187395022-0 404 (Not Found)

I did not do any modification in my `app.js` (project created by express &lt;project_name&gt;).

index.js:

    var express = require(&#39;express&#39;);
    var router = express.Router();
    var http = require(&#39;http&#39;);
    var fs = require(&#39;fs&#39;);
    var io = require(&#39;socket.io&#39;)(http);
    /* GET home page. */
    router.get(&#39;/&#39;, function(req, res) {
      res.render(&#39;index&#39;, { title: &#39;Express&#39; });
    });

    router.get(&#39;/home&#39;, function(req, res) {
      res.render(&#39;home&#39;, { title: &#39;Express&#39; });
    });

    io.on(&#39;connection&#39;, function(socket){
    	console.log(&quot;User Connected&quot;);
      socket.on(&#39;chat message&#39;, function(msg){
        io.emit(&#39;chat message&#39;, msg);
        console.log(&quot;Message&quot;);
      });
       socket.on(&#39;disconnect&#39;, function(msg){
        console.log(&quot;User DisConnected&quot;);
      });

    });

    router.post(&#39;/authenticate&#39;, function(req, res) {
     	fs.readFile(&quot;./public/Verification/Users.json&quot;, &quot;utf8&quot;, function (err, data) {
            if (err) 
            	console.log(err);
            else{
            	var result = JSON.parse(data);
             	for(var i=0;i&lt;result.Users.length;i++){
            		if(req.body.username == result.Users[i].username &amp;&amp; req.body.password ==     result.Users[i].password){
        		    	console.log(&quot;Success!!!!!!!!!!!!!!&quot;);
        	    		res.location(&quot;home&quot;);
                        res.redirect(&quot;home&quot;);
        	    	}
            	}
            }
            });
    });

    module.exports = router;

In my `layout.jade` I defined Socket.io like this:

    script(src=&#39;https://cdn.socket.io/socket.io-1.2.0.js&#39;)

    

How to resolve a Socket.io 404 (Not Found) error?

I have :

1. Apache 2.4 on port 80 of my server, with *[mod_proxy][1]* and *[mod_proxy_wstunnel][2]* enabled

2. Node.js + `socket.io` on port 3001 of the same server

Accessing `example.com` (with port 80) redirects to 2. thanks to [this method][3] with the following Apache configuration:

    &lt;VirtualHost *:80&gt;
        ServerName example.com
        ProxyPass / http://localhost:3001/
        ProxyPassReverse / http://localhost:3001/
        ProxyPass / ws://localhost:3001/
        ProxyPassReverse / ws://localhost:3001/
    &lt;/VirtualHost&gt;

It works for everything, except the websocket part : `ws://...` are not transmitted like it should by the proxy.

When I access the page on `example.com`, I have:

    Impossible to connect ws://example.com/socket.io/?EIO=3&amp;transport=websocket&amp;sid=n30rqg9AEqZIk5c9AABN.

Question: **How to make Apache proxy the WebSockets as well?** 


  [1]: https://httpd.apache.org/docs/2.4/mod/mod_proxy.html
  [2]: https://httpd.apache.org/docs/2.4/mod/mod_proxy_wstunnel.html
  [3]: https://stackoverflow.com/a/18604082/1422096

Content Type	Original Author	Original Content on Stackoverflow
Question	Abhishek Kaushik	View Question on Stackoverflow
Solution 1 - node.js	Oleg	View Answer on Stackoverflow

List of Socket.io Events

node.js Problem Overview

node.js Solutions

Solution 1 - node.js

Client-side events for `socket.io` object:

Client-side events for `socket` object:

Server-side events:

Edit:

How can I test binary file uploading with django-rest-framework's test client?

Check if color is dark or light in Android

Attributions

node.js Problem Overview

node.js Solutions

Solution 1 - node.js

Client-side events for socket.io object:

Client-side events for socket object:

Server-side events:

Edit:

How can I test binary file uploading with django-rest-framework's test client?

Check if color is dark or light in Android

Attributions

Client-side events for `socket.io` object:

Client-side events for `socket` object: