How to use the IncomingMessage function from http

core.js

GitHub: nwjs/node

3108
3109
3110
3111
3112
3113
3114
3115
3116
3117
  options.unknownProtocolTimeout = 10000;


// Used only with allowHTTP1
options.Http1IncomingMessage = options.Http1IncomingMessage ||
  http.IncomingMessage;
options.Http1ServerResponse = options.Http1ServerResponse ||
  http.ServerResponse;

options.Http2ServerRequest = options.Http2ServerRequest ||

42

19

0

mock-express.js

GitHub: kaiserbear/ghost-5.22.7

0
1
2
3
4
5
6
7
8
9
10
const _ = require('lodash');
const http = require('http');


module.exports = {
    invoke: function (app, reqParams) {
        let req = new http.IncomingMessage();
        let res = new http.ServerResponse({
            method: reqParams.method
        });

1

0

0

http.js

GitHub: maybesmurf/gitter

1
2
3
4
5
6
7
8
9
10
11
12
13


var http = require('http');
var useragent = require('useragent');


var ServerResponsePrototype = http.ServerResponse.prototype;
var IncomingMessagePrototype = http.IncomingMessage.prototype;


/* Monkey patch onto the response */
/*
 * This is needed as connect/express attempt to be too smart for their own good behind proxies (like NGINX) and convert relative URLS into absolute URLS. Unfortunately behind a proxy the URL will proably we wrong.

0

0

0