barreirocollege / usi-ntw-a1 Goto Github PK

When receiving a GET request, if the response is 404, try to send a body. If the host folder contains a 404.html file, its content shall be sent as response body.

The server should handle HTTP/1.1 connections.

Your code should be in a working state, without the need of modifications from the Instructors, and your submission must comply with the specified guidelines. Points will be deducted if the guidelines are not respected, if the code crashes, has compilation errors or does not execute, or if additional tools are needed for compilation/execution (like maven, gradle, etc.).

The server must answer client requests with the correct status code appropriate for the situation. Status codes 200, 201, 400, 403, 404, 405, 501 and 505 must be considered.

• GET
• PUT
• DELETE
• NTW22INFO

The server must accept a port number as an argument and it must listen for connections on said port. Use port 8080 as default.

The submission must include one site per group member.

• @AristeidisVrazitoulis
• @marinapapageorgiou
• @barreeeiroo

Sometimes, when issuing multiple requests, the request object is not being generated properly. For example, when issuing a GET request without a body, the server received a request object with a body (probably due to prior requests).

If request is well formatted, GET method must return error 415 Unsupported Media Type if server cannot recognize the MIME type of such file (and, consequently, cannot generate the Content-Type header).

The server should be able to answer well-formed PUT requests as specified by the corresponding RFCs.

The server should be able to answer well-formed GET requests as specified by the corresponding RFCs.

Your code must be appropriately documented and your submission must include a README file as a report of your work. The report must include compilation and execution steps, plus a table of contributions.

The server must be multithreaded.

The server should be able to answer to NTW22INFO requests as specified by the assignment.

The server should be able to answer well-formed DELETE requests as specified by the corresponding
RFCs.

The server should be able to read from a vhosts.conf file the information regarding the sites it serves.