C++ webserver(have most code just have to do fix me's and fill me's section)

**Project Stage 0 Specifications** For Stage 0, students are to implement a very basic HTTP server and client. Most of the code will be provided for. The code that is made available will have well marked “COMPLETE_ME?? portions missing that need to be completed. In addition, the code is to be extended to (i) gracefully handle any errors that might occur and in particular to gracefully handle possible buffer overflow situation, (ii) do extensive logging of errors and actions, and (iii) support persistent connections. The code also contains errors (some of which are marked with “FIXME??) that need to be fixed. Finally, the code provided is rather primitive and highly inefficient. You are free to improve the code by making it more sophisticated and more efficient. The client and server must properly be able to handle basic GET requests for files. That is, the Web client must be able to (i) open a connection to a target Web server, (ii) write out an HTTP request over the connection, (iii) read back the response, and (iv) interpret the response, and if a file is returned save the returned file to disk. The server must be able to (i) accept new connections, (ii) read requests from the connection, (iii) parse the URL, decomposing it into its fields according the HTTP protocol, (iv) if appropriate read the file from disk, and (v) formulate a response and send it back to the client over the connection. For persistent connections, the client must be modified to be able to request multiple objects over a single connection, and the server be able to process a sequence of requests and should not close the connection cont'd on... **please look in the operating platform section** ## Deliverables 1) Complete and fully-functional working program(s) in executable form as well as complete source code of all work done. 2) Deliverables must be in ready-to-run condition, as follows (depending on the nature of the deliverables): a) For web sites or other server-side deliverables intended to only ever exist in one place in the Buyer's environment--Deliverables must be installed by the Seller in ready-to-run condition in the Buyer's environment. b) For all others including desktop software or software the buyer intends to distribute: A software installation package that will install the software in ready-to-run condition on the platform(s) specified in this bid request. 3) All deliverables will be considered "work made for hire" under U.S. Copyright law. Buyer will receive exclusive and complete copyrights to all work purchased. (No GPL, GNU, 3rd party components, etc. unless all copyright ramifications are explained AND AGREED TO by the buyer on the site per the coder's Seller Legal Agreement). ## Platform The operating system is going to be Linux. **cont...** The Web client and server will have a number of limitations, including: • they only need to support the GET request with no parameters; • they only need to support requests for static files (that exist); • the only request header that needs to be included is Host; • the only response headers that need to be included are Content-Length and Content-Type; and • only one request needs to be processed by the server at a time, and with persistent connections, only 1 connection needs to be processed at a time; i.e. no concurrency is required. These limitations will be eliminated in later stages of the project. **The detailed discription of all the classes are defined in the PDF file called Project Specification: STAGE 0 click on handout section** [**[login to view URL]**][1]