Using Meteor without opening a Port

diaconutheodor · May 11, 2017, 6:27am

We coded some job workers for a project, but we don’t really need it to be an http server. How do we shut that down ?

Thank you!

herteby · May 11, 2017, 9:52am

You probably know a lot more than me about Meteor, having created Grapher and all. But what if you just remove “browser” from .meteor/platforms?
And what’s the harm in having meteor listening to some random port on your server, that you don’t expose to the outside anyway?

diaconutheodor · May 11, 2017, 10:02am

@herteby actually i think you’re right, it shouldn’t matter if a port is opened if it’s not accessed. But having it open may open the way of each job worker to expose an http api.

robfallows · May 11, 2017, 11:30am

Looking at the webapp package, it seems you may be able to restrict listening to localhost by setting BIND_IP:

github.com

meteor/meteor/blob/devel/packages/webapp/webapp_server.js#L811-L832


});




var httpServer = createServer(app);
var onListeningCallbacks = [];


// After 5 seconds w/o data on a socket, kill it.  On the other hand, if
// there's an outstanding request, give it a higher timeout instead (to avoid
// killing long-polling requests)
httpServer.setTimeout(SHORT_SOCKET_TIMEOUT);


// Do this here, and then also in livedata/stream_server.js, because
// stream_server.js kills all the current request handlers when installing its
// own.
httpServer.on('request', WebApp._timeoutAdjustmentRequestCallback);


// If the client gave us a bad request, tell it instead of just closing the
// socket. This lets load balancers in front of us differentiate between "a
// server is randomly closing sockets for no reason" and "client sent a bad
// request".

This file has been truncated. show original

rhywden · May 11, 2017, 12:43pm

Or simply use iptables and drop everything for that port?