fhash | fHash - an open source files hash calculator for Windows | Cryptography library

Do not close your connection in the db_connect function and you need to return a conn from this function as well.

It looks like your algorithm duplicates entries or you manually generated getters and setters which duplicate output. By default Jackson does not add extra entries. See below example how you can do that, I generated getters and setters in IDE. f-fieldName pattern for fields is outdated and you should use regular names. See, for example, Google's Java Guide:

You are making two big mistakes:

1. Your OnConnect event handler is reading the client's initial HTTP request line (the GET line). It should not be reading anything from the client at all, as doing so interfers with TIdHTTPServer's handling of the HTTP protocol.

   After the event handler reads the request line and exits, TIdHTTPServer then reads the next line (the Host header) and interprets that as the request line instead, which is why:

   • the ARequestInfo->Command property is "HOST:" instead of "GET".

   • the ARequestInfo->Host, ARequestInfo->Document, ARequestInfo->Version, ARequestInfo->VersionMajor, ARequestInfo->VersionMinor properties are all wrong.

   • you end up having to use the OnCommandOther event when you should be using the OnCommandGet event instead.

2. You are accessing the TMemo in your TIdHTTPServer events without synchronizing with the main UI thread. TIdHTTPServer is a multi-threaded component. Its events are fired in the context of worker threads. VCL/FMX UI controls are not thread-safe, so you must synchronize properly with the main UI thread.

Your server is not validating everything in the handshake that the WebSocket protocol requires a server to validate (which is fine for testing, but make sure you do it for production).

But more importantly, TIdHTTPServer is not well-suited for implementing WebSockets (that is a TODO item). The only thing about the WebSocket protocol that involves HTTP is the handshake. After the handshake is finished, everything else is WebSocket framing, not HTTP. To handle that in TIdHTTPServer requires you to implement the entire WebSocket session inside of the OnCommandGet event, reading and sending all WebSocket frames, preventing the event handler from exiting, until the connection is closed. For that kind of logic, I would suggest using TIdTCPServer directly instead, and just handle the HTTP handshake manually at the beginning of its OnExecute event, and then loop the rest of the event handling the WebSocket frames.

Your OnCommandOther event handler is not currently performing any WebSocket I/O after the handshake is finished. It is returning control to TIdHTTPServer, which will then attempt to read a new HTTP request. As soon as the client sends a WebSocket frame to the server, TIdHTTPServer will fail to process it since it is not HTTP, and will likely send an HTTP response back to the client, which will get misinterpreted, causing the client to fail the WebSocket session and close the socket connection.

With that said, try something more like this instead: