Build a simple HTTP server in C [closed]

Question

I need to build a simple HTTP server in C. Any guidance? Links? Samples?

Williswillison

I got the same question and somehow I got incomplete but very simple implementation(incomplete) using C, which compiles under Ubuntu linux thought it would be valuable if I tag it here, blog.abhi.host/blog/2010/04/15/… – Bilbao

Answer 1

I suggest you take a look at tiny httpd. If you want to write it from scratch, then you'll want to thoroughly read RFC 2616. Use BSD sockets to access the network at a really low level.

Codicodices

Or use inetd and skip the networking part. – Conscription

Don't read RFC 2616 now, it obsoleted by: RFC 7230, RFC 7231, RFC 7232, RFC 7233, RFC 7234, RFC 7235 – Entice

tiny httpd is also on github here: github.com/larryhe/tinyhttpd – Pucka

Answer 2

I'd recommend that you take a look at: A Practical Guide to Writing Clients and Servers

What you have to implement in incremental steps is:

1. Get your basic TCP sockets layer running (listen on port/ports, accept client connections and send/receive data).
2. Implement a buffered reader so that you can read requests one line (delimited by CRLF) at a time.
3. Read the very first line. Parse out the method, the request version and the path.
4. Implement header parsing for the "Header: value" syntax. Don't forget unfolding folded headers.
5. Check the request method, content type and content size to determine how/if the body will be read.
6. Implement decoding of content based on content type.
7. If you're going to support HTTP 1.1, implement things like "100 Continue", keep-alive, chunked transfer.
8. Add robustness/security measures like detecting incomplete requests, limiting max number of clients etc.
9. Shrink wrap your code and open-source it :)

Downgrade

Point #9, especially after posting a question here, +1 :) – Lenlena

Thank you for providing concepts rather than prebuilt solutions or links to RFC and Sockets. Reading the RFC and learning about Sockets isn't enough to build your own web server if you don't have these concepts in mind. – Homicidal

Reading requests line by line using "a buffered reader" (hence storing the line in a buffer until we find a CRLF), makes me anxoius about attacks that send gigabytes of data without CRLF. For this, I usually read using 'states', re-allocate the buffers on the go with the data, check for limits every read and send 414 appropriately. Except point #2, I agree with all the other points. – Leviticus

Answer 3

An HTTP server is conceptually simple:

• Open port 80 for listening
• When contact is made, gather a little information (get mainly - you can ignore the rest for now)
• Translate the request into a file request
• Open the file and spit it back at the client

It gets more difficult depending on how much of HTTP you want to support - POST is a little more complicated, scripts, handling multiple requests, etc.

But the base is very simple.

Mobilize

Thank you for providing concepts rather than prebuilt solutions or links to RFC and Sockets. Reading the RFC and learning about Sockets isn't enough to build your own web server if you don't have these concepts in mind. – Homicidal

Answer 4

Mongoose (Formerly Simple HTTP Daemon) is pretty good. In particular, it's embeddable and compiles under Windows, Windows CE, and UNIX.

Benzine

Answer 5

Open a TCP socket on port 80, start listening for new connections, implement this. Depending on your purposes, you can ignore almost everything. At the easiest, you can send the same response for every request, which just involves writing text to the socket.

Dibasic

Answer 6

Look at nweb (Nigel's Web Server), "a tiny, safe web server [...] with only 200 lines of C source code":

https://drive.google.com/file/d/0B3msld7qnNOhN1NXaFIwSFU2Mjg/view?usp=sharing&resourcekey=0-ngY0neP78dxJKlFv0PJoDQ http://www.ibm.com/developerworks/systems/library/es-nweb/

The article includes pseudocode, explanations, and comments.

EDIT: IBM's link has died. I have saved a PDF of the webpage to Google Drive. Here is the code download:

https://drive.google.com/file/d/0B3msld7qnNOhSGZGdDJJMmY0VHM/view?usp=sharing&resourcekey=0-xkbf4mv0gN1sZrhBjt86UQ

@ankushagarwal has made a few changes and uploaded his version on GitHub: https://github.com/ankushagarwal/nweb

Khelat

Eh up voted without checking link :/ I'm looking for the exact thing you mentioned, if you find something can you ping me? Txt – Lacuna

@Lacuna IBM's link has died. I have provided some mirrors. – Khelat

Here's a mirror by archive.org - which will hopefully be around for years to come: web.archive.org/web/20140905115151/http://www.ibm.com/… – Coldblooded

Answer 7

I have written my own that you can use. This one works has sqlite, is thread safe and is in C++ for UNIX.

You should be able to pick it apart and use the C compatible code.

http://code.google.com/p/mountain-cms/

Mixtec

Answer 8

The HTTP spec and Firebug were very useful for me when I had to do it for my homework.

Good luck with yours. :)

Extractor

Answer 9

I'd suggest looking at the source to something like lighthttpd.

Trigg

Answer 10

http://www.manning.com/hethmon/ -- "Illustrated Guide to HTTP by Paul S. Hethmon" from Manning is a very good book to learn HTTP protocol and will be very useful to someone implementing it /extending it.

Grandchild

Answer 11

There is a duplicate with more responses.

One candidate not mentioned yet is spserver.

Benuecongo

Answer 12

Use platform specific socket functions to encapsulate the HTTP protocol, just like guys behind Apache did.

Burrussburry

But... Apache Server is the complete opposite of "simple"? – Fluke