As well as serving your static content, CloudFront supports the delivery of dynamic content to the users by giving us the ability to configure the session HTTP/HTTPS termination at the CloudFront location. This feature allows us to secure and accelerate any application running either WebSockets or API calls. CloudFront can proxy the following HTTP methods to the origin servers or to the API Gateway:

• GET: A read operation against a HTTP server. Used for caching static content. GET retrieves a document.
• HEAD: Like GET it also reads, but HEAD retrieves just the header of the document without retrieving the body.
• POST: A write operation against a HTTP server that is commonly used to send textual information. CloudFront can proxy the POST request and deliver the content to the target more quickly through the AWS backbone.
• PUT: Like POST it also writes, but encloses a file or data blob that is to be stored on the server.
• OPTIONS: A general request to the server inquiring about the communication options available.
• DELETE: A write request to delete a certain resource on the HTTP server.
• PATCH: A write request designed as an extension to PUT that enables the requestor to modify an existing file or data blob on an HTTP server. Instead of re-uploading the whole file with PUT, we can use PATCH to upload only a certain section of bytes within the file itself.