Websrv Alternatives

Similar projects and alternatives to websrv

src

745 3,044 10.0 C websrv VS src

Read-only git conversion of OpenBSD's official CVS src repository. Pull requests not accepted - send diffs to the tech@ mailing list.
cosmopolitan

201 15,180 9.8 C websrv VS cosmopolitan

build-once run-anywhere c library
InfluxDB

www.influxdata.com featured

Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
libuv

75 23,241 9.0 C websrv VS libuv

Cross-platform asynchronous I/O
Mongoose

32 10,602 9.6 C websrv VS Mongoose

Embedded Web Server (by cesanta)
nanos

27 2,468 9.2 C websrv VS nanos

A kernel designed to run one and only one application in a virtualized environment
picohttpparser

3 1,782 4.2 C websrv VS picohttpparser

tiny HTTP parser written in C (used in HTTP::Parser::XS et al.)
epoll-server

3 8 3.3 C websrv VS epoll-server

C code for multithreaded multiplexing client socket connections across multiple threads (so its X connections per thread) uses epoll
SaaSHub

www.saashub.com featured

SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
libreactor

1 379 0.0 C websrv VS libreactor

Extendable event driven high performance C-abstractions
libhttp

1 926 2.3 C websrv VS libhttp

Multi platform HTTP and HTTPS library

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a better websrv alternative or higher similarity.

Suggest an alternative to websrv

websrv reviews and mentions

Posts with mentions or reviews of websrv. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2022-12-18.

Ask HN: Resources for Building a Webserver in C?
10 projects | news.ycombinator.com | 18 Dec 2022

"Write a tiny web server in C" was a standard exercise when I was in high school, and later again in university. I think I did that at least 3 times as an assignment so far.
Back in 2015, I dumped the result of the University exercise here: https://github.com/AgentD/websrv and kept adding to it for fun.
The HTTP 1.x protocol itself is pretty dead simple (if you ignore chunked requests/responses and such) and the more interesting part was actually the socket code.
Back in school, our teacher had us write a simple forking server and consult the corresponding man pages (man 2 socket, man 7 socket, man 7 tcp). It was an acceptable minimal solution to not even look at the client request, respond with a static string containing a dummy response header and HTML page, which absolutely works. Bonus points for parsing the request path and sending a file back, more extra points if the path was a directory and your server sends back an "index.html" file, further points if it instead generates an HTML directory listing on the fly.
When I visited our former teacher a couple years ago, he had modified the exercise somewhat. He brought a Beagle Bone Black with him to class, with a bunch of I2C sensors attached to it, and the extended exercise revolve around reporting temperature/humidity/... to the browser.
So, for "resource" I recommend the HTTP example on Wikipedia, as well as "Beej's guide to network programming" (as have others), as well as the man pages for quick reference.