connect

I'm trying to start serving some static web pages using connect like this: var connect = require("connect"); var nowjs = require("now"); var io = require("socket.io"); var app = connect.createServer( connect.static(__dirname + '/public') ); app.listen(8180); So I added a simple index.html at the /public directory on the same directory as the app.js file is, but when I try to view the page on my browser I get this response from node: Cannot GET / What I'm doing wrong and how I can correct it? This code should work: var connect = require("connect"); var app = connect.createServer().use(connect

Scenario : Consider the following is the part of code from a node web app. app.get('/users/:id?', function(req, res, next){ var id = req.params.id; if (id) { // do something } else { next(); //or return next(); } }); Issue : I am checking which one to go with just next() or return next() . Above sample code works exactly the same for both & did not show any difference in execution. Question : Can some one put light on this, when to use next() and when to use return next() and some important difference? Some people always write return next() is to ensure that the execution stops after

I am trying to figure out what "signed cookies" actually are. There isn't much on the net, and if I try this: app.use(express.cookieParser('A secret')); But still... Cookies are still 100% normal on the browser, and I don't really know what "signed" is here (I was sort of hoping to "see" some weirdness on the client, something like the data encrypted using "A secret" as salt?) The documentation says ( https://github.com/expressjs/cookie-parser ): Parse Cookie header and populate req.cookies with an object keyed by the cookie names. Optionally you may enabled signed cookie support by passing a

I am trying to parse an XML file from an HTTP URL. I want to configure a timeout of 15 seconds if the XML fetch takes longer than that, I want to report a timeout. For some reason, the setConnectTimeout and setReadTimeout do not work. Here's the code: URL url = new URL("http://www.myurl.com/sample.xml"); URLConnection urlConn = url.openConnection(); urlConn.setConnectTimeout(15000); urlConn.setReadTimeout(15000); urlConn.setAllowUserInteraction(false); urlConn.setDoOutput(true); InputStream inStream = urlConn.getInputStream(); InputSource input = new InputSource(inStream); And I am catching

This seems like it should be a fairly simple question, but I'm having a really hard time figuring out how to approach it. I'm using Node.js + Express to build a web application, and I find the connect BodyParser that express exposes to be very useful in most cases. However, I would like to have more granular access to multipart form-data POSTS as they come - I need to pipe the input stream to another server, and want to avoid downloading the whole file first. Because I'm using the Express BodyParser, however, all file uploads are parsed automatically and uploaded and available using "request

I want to be able to host multiple NodeJS apps under the same domain, without using sub-domains (like google.com/reader instead of images.google.com). The problem is that I'm always typing the first part of the url e.g. "/reader" in Express/NodeJS. How can I set up an Express app so that the base URL is something.com/myapp ? So instead of: app.get("/myapp", function (req, res) { // can be accessed from something.com/myapp }); I can do: // Some set-up app.base = "/myapp" app.get("/", function (req, res) { // can still be accessed from something.com/myapp }); I'd also like to configure Connect's