Server: header length limit, smart send, header end timeout, cgi location

[andreaulicna]

• Header length limit & infinite send protection

  • hasValidHeaderEnd checks for the buffer being longer than CLIENT_MESSAGE_BUFF * 2 (without finding the valid header end) and throws 413 if so

• Send to send everything:

  • Send to send everything if not enough space in client socket:
  • send returns send bytes or -1, so:
    • if sent bytes < message size, erase sent bytes from the buffer and send the rest in the next go (keeping the socket in write)
    • on -1 close connection
  • Buff allocation:
  • only what's neccessary gets allocated
  • max. 8 KB, longer messages get split between multiple sends (logic of the 1st bullet point))
  • Send to send everythig if message longer than 8 KB buffer
  • erase sent bytes and send the rest in the next go (keeping the socket in write)

• Timeout for sending valid header end

  • checkForTimeout now checks 2 timestamps: _timeLastMessage, _timeLastValidHeaderEnd

• New structure of CGI location in server config

FYI @loudapet - first 3 bullet points are relevant for you too