@types/connect

property originalUrl

originalUrl?: any;

property route

route: string;

property stack

stack: ServerStackItem[];

method handle

handle: (
    req: http.IncomingMessage,
    res: http.ServerResponse,
    next: Function
) => void;

• Handle server requests, punting them down the middleware stack.

method listen

listen: {
    (
        port: number,
        hostname?: string,
        backlog?: number,
        callback?: Function
    ): http.Server;
    (port: number, hostname?: string, callback?: Function): http.Server;
    (path: string, callback?: Function): http.Server;
    (handle: any, listeningListener?: Function): http.Server;
};

• Listen for connections.

  This method takes the same arguments as node's http.Server#listen().

  HTTP and HTTPS:

  If you run your application both as HTTP and HTTPS you may wrap them individually, since your Connect "server" is really just a JavaScript Function.

  var connect = require('connect') , http = require('http') , https = require('https');

  var app = connect();

  http.createServer(app).listen(80); https.createServer(options, app).listen(443);

method use

use: {
    (fn: NextHandleFunction): Server;
    (fn: HandleFunction): Server;
    (route: string, fn: NextHandleFunction): Server;
    (route: string, fn: HandleFunction): Server;
};

• Utilize the given middleware handle to the given route, defaulting to _/_. This "route" is the mount-point for the middleware, when given a value other than _/_ the middleware is only effective when that segment is present in the request's pathname.

  For example if we were to mount a function at _/admin_, it would be invoked on _/admin_, and _/admin/settings_, however it would not be invoked for _/_, or _/posts_.

call signature

(req: http.IncomingMessage, res: http.ServerResponse, next?: Function): void;

property handle

handle: ServerHandle;

property route

route: string;