Build a simple HTTP server in C

Question

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

User · Answer

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

User · Answer

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

User · Answer

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

User · Answer

Mongoose  Formerly Simple HTTP Daemon  is pretty good  In particular  it s embeddable and compiles under Windows  Windows CE  and UNIX

User · Answer

The HTTP spec and Firebug were very useful for me when I had to do it for my homework   Good luck with yours

User · Answer

The HTTP spec and Firebug were very useful for me when I had to do it for my homework   Good luck with yours

User · Answer

Mongoose  Formerly Simple HTTP Daemon  is pretty good  In particular  it s embeddable and compiles under Windows  Windows CE  and UNIX

User · Answer

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

User · Answer

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

User · Answer

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

User · Answer

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

User · Answer

Mongoose  Formerly Simple HTTP Daemon  is pretty good  In particular  it s embeddable and compiles under Windows  Windows CE  and UNIX

User · Answer

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

User · Answer

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

User · Answer

Mongoose  Formerly Simple HTTP Daemon  is pretty good  In particular  it s embeddable and compiles under Windows  Windows CE  and UNIX

User · Answer

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

User · Answer

There is a duplicate with more responses   One candidate not mentioned yet is spserver

User · Answer

I d suggest looking at the source to something like lighthttpd

User · Answer

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

User · Answer

I d suggest looking at the source to something like lighthttpd

User · Answer

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

User · Answer

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

User · Answer

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

User · Answer

The HTTP spec and Firebug were very useful for me when I had to do it for my homework   Good luck with yours

User · Answer

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

User · Answer

I d suggest looking at the source to something like lighthttpd

User · Answer

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

User · Answer

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 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   ankushagarwal has made a few changes and uploaded his version on GitHub  https   github com ankushagarwal nweb

User · Answer

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

User · Answer

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

User · Answer

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

User · Answer

The HTTP spec and Firebug were very useful for me when I had to do it for my homework   Good luck with yours

User · Answer

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

User · Answer

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

User · Answer

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

User · Answer

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

User · Answer

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

User · Answer

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

User · Answer

There is a duplicate with more responses   One candidate not mentioned yet is spserver

User · Answer

I d suggest looking at the source to something like lighthttpd

User · Answer

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 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   ankushagarwal has made a few changes and uploaded his version on GitHub  https   github com ankushagarwal nweb

User · Answer

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

User · Answer

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

User · Answer

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

[c] Build a simple HTTP server in C

Examples related to c

Examples related to httpserver