connect

I am attempting to have the server handle a PUT request. But to no avail. The client keeps receiving "Cannot POST /" message after submitting the form. I am using Express 4.x. Note that if I change "put" to "post" in my route, the request gets handled just fine... How can I have my server handle the 'PUT' request? SERVER: var express = require("express"); var bodyParser = require("body-parser"); var methodOverride = require("method-override"); var app = express(); app.use(bodyParser()); app.use(methodOverride()); app.get("/",function(req,res){ res.render("index.ejs"); console.log("GET received

I would like to know what are the functions the Error object of nodejs express exposes for use in Error Handling? A console.log of an error call new Error('NotFound') is showing only [Error: NotFound] , is this because .toString() method is overriden? How do find the properties and functions exposed by these objects? The Error object is actually a native object provided by V8 , rather than by node.js or express . The property that will most likely be of the most use to you is stack . E.g., console.log(new Error('NotFound').stack); There are other properties available as well, such as name and

I have an application using NodeJS, Express, MongoDB and connect-mongo. My issue is that sessions don’t seem to be automatically deleted from MongoDB when they expire, so the db size grows until the disk is full. The developer of connect-mongo wrote a comment : connect-mongo will ask MongoDB to remove all the sessions that have expired before the current date. But this doesn’t seem to be happening in my case. My configuration is: var express = require('express'); var MongoStore = require('connect-mongo'); var sessionStore = new MongoStore({db: 'myappsession'}); var app = express.createServer()

I'm using node.js with Express and connect-auth to authenticate users. This is the verification when requesting /index: if(req.isAuthenticated()) { res.redirect('/dashboard'); } else { res.render('index', { layout: 'nonav' }); } However, after logging out and going back to f.e. '/dashboard', I can see the dashboard. How can I put the authentication check to every request to make sure there's a valid user at all times? Update I don't have any problems with the authentication, everything works fine! I need a solution which checks every route/request if there's a valid user, without putting a

Farmer John has been elected mayor of his town! One of his campaign promises was to bring internet connectivity to all farms in the area. He needs your help, of course. Farmer John ordered a high speed connection for his farm and is going to share his connectivity with the other farmers. To minimize cost, he wants to lay the minimum amount of optical fiber to connect his farm to all the other farms. Given a list of how much fiber it takes to connect each pair of farms, you must find the minimum amount of fiber needed to connect them all together. Each farm must connect to some other farm such

how can I connect these entity boxes? the boxes are created by clicking a button and they can be dragged. Now I want to connect them with a line or something. Here is a quick and dirty implementation: the class that represents the connection: public partial class Connection { public MyBox Box1 { get; set; } public MyBox Box2 { get; set; } public Line Line { get; set; } } To create a new connection I've used a basic form: name of source, destination and a button: <StackPanel Orientation="Horizontal" Grid.Row="3"> <TextBox Width="100" Text="{Binding From,UpdateSourceTrigger=PropertyChanged,Mode

I'm reading Node.js Connect version 2.15.0: /** * Create a new connect server. * * @return {Function} * @api public */ function createServer() { function app(req, res, next){ app.handle(req, res, next); } utils.merge(app, proto); utils.merge(app, EventEmitter.prototype); app.route = '/'; app.stack = []; for (var i = 0; i < arguments.length; ++i) { app.use(arguments[i]); } return app; }; A few questions: app.handle seems to be provided in proto, since there is app.handle defined in proto.js. So, this is a use of a closure, and app.handle is defined not at the time Node parses function app() but