Qfyilyi

I have a local web server on which I can handle invalid HTTP packages. For example ones that do not start with standard HTTP header methods like GET POST PUT etc...

Thus I can analyze socket data even if it is not HTTP compliant.
This is the code:

var express = require("express");

var app = express();

var server = app.listen(process.env.PORT || 5000);



app.get("/", (req, res) => {

  res.send("Hello Riko");

});



onSocketError = err => {

  console.log("Socket Error: " + err);

};



server.on("connection", function(socket) {

  socket.on("data", data => {

    console.log(data.toString());

  });

  console.log("A new connection was made by a client.");

});

server.on("clientError", (err, socket) => {

  console.log("CLIENT ERROR!");

  socket.removeAllListeners("error");

});

Running it on Heroku, does't work the same. I responds on TCP client request:

GET / HTTP/1.1rnHost: rikoto.herokuapp.comrnrn

as expected. The response message is:

+IPD,246:HTTP/1.1 200 OK

Server: Cowboy

Connection: keep-alive

X-Powered-By: Express

Content-Type: text/html; charset=utf-8

Content-Length: 10

Etag: W/"a-1i9Fh6ETfQADte3Iit4UFXuXMKs"

Date: Thu, 22 Nov 2018 15:09:25 GMT

Via: 1.1 vegur



Hello Riko

But this code:

server.on("clientError", (err, socket) => {

  console.log("CLIENT ERROR!");

  socket.removeAllListeners("error");

});

that works perfectly on my local machine is ignored by Heroku.
This is the app link: https://rikoto.herokuapp.com/

***** EDIT *****
I attached a video to demonstrate the problem: https://youtu.be/c-Q7ge7cuFA