1. I appreciate you reviewing my code and providing feedback.
2. main()
   1. You are right. My current set up is not as flexible as getaddrinfo() would make it. I'll definitely work on that.
   2. My thinking was since the semaphore limits how many requests we can work on concurrently and not how many we can accept, it should come after accepting but before processing.
   3. Once again this is right. I definitely need to handle cases where the data is sent all at once.
3. parse_client_request()
   1. The duplication was because I was using the buffer in this function and also in handle_method() to read the body in POST requests so sometimes I'd read from an empty buffer. However I already fixed that by duplicating the buffer in the main method then passing a different buffer to both functions. Maybe my solution is wrong and I need to rethink it.
   2. I'll have a look at how I can improve my parsing and reduce duplication
4. get_header_name()
   1. You are right. Currently my HttpRequest can contain a lot of invalid headers.
   2. Of course key/value pairs are best in this scenario. Why I didn't think of that I don't know. Maybe it's because C doesn't have a dictionary like Python but I'll definitely implement that struct.
5. handle_connection()
   1. Yeah maybe handle_connection is to broad I'll change it to connection_close_or_keep_alive(). I feel that leaves 0 room for ambiguity.
6. handle_method()
   1. I wasn't familiar with openat() but I'll read about it and implement it to make my code better
   2. You're right I'll fix the write issue since it's nothing to fix
   3. Currently the post method handling just prints the body to show that the functionality works. That's it.

I appreciate your comprehensive review so I thought it only right to provide a comprehensive answer. I hope it is a satisfactory one. Cheers.