The better approach is to put your own HTTP server behind a reverse proxy like nginx or apache. This has several advantages:
1. The reverse Proxy implements modern protocols and features like IPv6 support, OpenSSL 3, HTTP 2, etc.
2. A popular reverse proxy solution like nginx or apache is much better audited and supported and gets feature and security updates much faster than fpc
3. The reverse Proxy implements caching for static assets and load balancing with containerization services. So you can focus an writing a very simple HTTP handler and still get the performance benefits from a high performance and scalable system
4. the Reverse Proxy manages all your SSL certificates (like via lets encrypt) so you do not have to deal with SSL in your own server.
Infact, especially because of the security concerns and the slow update cycle, it would be quite irresponsible to not use a reverse proxy if you want to make your service accessible through the internet