HTTP 1.1 Server

• Forces browsers to check cache validity on every request
• Uses 304 response whenever possible
• Applies ETags to views in order to avoid browser confusion
  
• Offers GZIP compression
• Maps every incoming request to a specific project, whose pipelines are then used to generate the output
• Uses request/response API whose default implementations enable it to run as a servlet.