Your described use case for a "friendly / internal" system has a limited definition in any non-trivial sized organization. It would only apply when all users of the embedded webserver already have root access to that server. This might make sense, for instance, in a small development team with a flat security hierarchy, but would be a red flag, security wise, otherwise.
>Your described use case for a "friendly / internal" system has a limited definition in any non-trivial sized organization.
Facebook is a non-trivial size company that has lots of internal private-facing programs with embedded http connectivity. From that experience, they open sourced Proxygen http library which is one of the links I mentioned in the previous comment.
Also, see the comment from VikingCoder which in turn links to reddit thread mentioning another big company like Google doing similar use cases with http libraries:
https://news.ycombinator.com/item?id=15671936
Facebook is a mixed bag as far as being a model of good behavior on many things. The company is founded on irresponsible social principles. For how long did general internal employees have access to users' private data? This is no longer the case, though, correct? Sorry to get OT.
Maybe these libs are well-vetted, after all. My mistake. Thanks for the info.
