The status codes below detail how Cloudflare interprets the Internet standards track protocol for HTTP response codes. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol.
Any HTTP status code that is cacheable by default will also be considered to be cacheable by Cloudflare unless otherwise indicated by the method definition or explicit cache controls. Cloudflare caches HTTP responses similarly to how any request is cached. Cloudflare considers page rules, edge TTL, and origin headers when deciding whether to cache.
HTTP status codes terms
The terms used when describing Cloudflare HTTP status codes are as follows:
Any party receiving a request and sending a response. Either the origin or intermediate servers.
The final destination server. This server actually hosts the content of the website.
The server(s) that sit between the origin server and the client. Cloudflare is a proxy server for example.
The party making the request. Typically an end user accessing the site on a browser, but may also be an API client or anyone requesting resources from the site.
The connections not made to or from the client, but between the proxy server(s) and/or the origin server
The machine used to send the request. Can be a browser or another program making requests (e.g. restful API requests)
The response or request data discluding the headers. Also called response/request body.