Wt's own HTTP Server for Production
Added by Isaac Lascasas almost 9 years ago
Hello.
I would like to know the main differences between using the bundled http server and using Apache for example. I am about to deploy and I need to know the catches. I don't have real experience with apache or web administration in general so I would prefer to just execute my program without extra hassle. The web requires high security.
Should I be ready to go just by enabling https within wthttp?
Thanks.
Isaac.
Replies (1)
RE: Wt's own HTTP Server for Production - Added by Koen Deforche almost 9 years ago
Hey,
Yes, wthttpd can be used directly, and offers a number of benefits (WebSockets being one of them), but also a simpler deployment setup and less hassle.
An alternative which is sometimes needed is to put wthttpd behind a reverse proxy such as HAProxy in case you also want some other daemons to listen to HTTP ports, e.g. for static content or if you have multiple applications. HAProxy is a good choice because it also forwards WebSockets traffic.
Putting wthttpd behind apache can be done, but then you will loose the ability to support WebSockets.
Koen