bodyparser | Automatically parse request.Body | HTTP library

Edit page2.html in both app.js post and html form action to page2

The object you want to save

In the login function, you are sending username and password as a key and accessing wrong keys on the server-side:

Can you log the req.body (console.log(req.body)) before using parseInt(req.body.f) and let us know what you get please?

I think it's something related to parsing.

Regards,

You redirect user to /login route, but you don't have get request for this.

If you have it but not uploaded try this in Seralize Passport

Well socket objects in nodejs belong to a particular process. You can't just share them with another process easily. If you want one process to cause data to be sent on a socket the other process owns, then send the data itself to the other process using a different server and send some identifier with the data that the receiving process can use to figure out which socket the data should be sent to and it will then send the data over the socket it has. But, this whole thing sounds like a really confusing way to do things.

For example, let's say you have serverTCP (the plain TCP server from your server.js) and serverAPI (an Express server from your other file) each in separate processes. Put a separate Express server in serverTCP running on a local port, not open to the outside world. When serverAPI receives some data for some socketID, it then makes an http request to serverTCP and sends the data and the socketID. serverTCP receives that http request, gets the socketID and the data out of that request and sends it out over the appropriate socket it has a connection to.

FYI, this is generically known as a proxy where your API is somewhat serving as a proxy for the real socket connection. There are all sorts of modules in NPM that implement actual proxies too.

Do console.log(req.body) first, if you can't read the data, check 3 things.

1. Check if server router HTTP method is one of post, put, delete
2. Check if browser side HTTP calls right method and argument ex>axios.post(url, data, config)
3. Check if body parser is attached in same context. For example, if you did app.use(bodyParser()) , all sub routes should be attached into app to refer req.body

If this check list doesn't work for you, please share client-side code and server-siderouter code for details.

Because new kafka.Client() isn't a constructor.

I guess it should be new kafka.KafkaClient()

If you're using the new node version( v14+) and Express v4.16.0 onwards, replace

router.use(bodyParser.json());

with

router.use(express.json());