benchaimberg / rust-http-server Goto Github PK

https://datatracker.ietf.org/doc/html/rfc7230#section-4.1

If the URL ends with / without specifying a file name, your server should return index.html if it exists; otherwise it will return Not Found.

If the mapped file is a static file (not executable), your server should be able to detect content type by file name suffix, including (.txt, .html, .jpg).

The server should have a timeout function. If a new connection does not give a complete request to the server approximately within timeout from the time of being accepted, the server should disconnect the connection. The timeout value is 3 seconds.

If the request URL is for DocumentRoot (i.e., empty URL) without specifying a file name and the User-Agent header indicates that the request is from a mobile handset (e.g., it should at least detect iphone by detecting iPhone in the User-Agent string), it should return index_m.html, if it exists; index.html next, and then Not Found.

Currently, the server returns responses encoded by chunks if the response is greater than a certain size. This is not really the proper use of chunked response encoding. What we should do is use chunked response encoding when the underlying resource is a stream of bytes (the stdout of a CGI script, for example). This requires incremental parsing and would be probably nicer to implement if we hook it in to the selector system.

Heatbeat monitoring: Your server needs to implement a heartbeat monitoring URL service to integrate with a load balancer (e.g., Amazon Load Balancer). In particular, a load balancer may query a virtual URL (i.e., no mapped file) named load (i.e., with request GET /load HTTP/1.0). If the server is willing to accept new connections, it should return status code 200; otherwise, it returns code 503 to indicate overloading. Please describe a particular design and implement it.