Check the code and ask question

Launch the installation of siege with homebrew Ask to get an explanation of how select is working. Ask if there is only one select and how they've managed the server accept and the client read/write. The select should be in the main loop and should check fd for read and write AT THE SAME TIME, if not please give a 0 and stop the evalaution. There should be only one read or one write per client per select. ASK to show you the code that goes from the select th the read and write of a client. Search for all read/recv/write/send on a socket and check that if an error returned the client is removed. Search for all read/recv/write/send and check if the returned value is well checked.(checking only -1 or 0 is not good you should check both) If a check of errno is done after read/recv/write/send. Please stop the evaluation and put a mark 0. Writing or reading ANY file descriptor without going through the select is strictly FORBIDDEN.

Configuration (TEAM2)

  1. setup multiple servers with different port

    포트가 다른 여러 개의 서버를 설정

  2. setup multiple servers with different host name (use something like curl --resolve ~~) 호스트 이름이 다른 여러 개의 서버를 설정

  3. setup default error page (try to change the error 404)

    디폴트 오류 페이지 설정(404 error를 변경하도록 시도)

  4. limit the client body

    클라이언트의 바디를 제한

  5. setup routes in a server to different directories

    서버의 루트들을 다른 디렉토리들로 설정

  6. setup a list of method accepted for a certain route (ex: setup only HEAD on a route and use curl with and without option -X HEAD)

    일정한 노선으로 통용되는 메소드 목록을 설정

Run the Tester

Check Headers (TEAM3)

open the RFC 7231 and check the list of header of the subject, ask questions about it.

RFC 7231 를 오픈해서 서브젝트의 헤더 목록을 확인하고, 헤더들에 대해 질문을 해보세요.

Use a browser, open the network park of it and try to connet to the server with it.

브라우저의 개발자도구에서 network 파트를 열어서 해당 서버에 연결을 시도해보세요.

Look at the request header and response header

요청헤더와 응답헤더를 확인하세요.

Try wrong URL on the server

잘못된 URL 요청을 해보세요.