Add logs for the controller

[karpetrosyan]

DEBUG Logs that have been added

logs for constructing response from the cache

Considering the resource located at https://example.com as valid for cache use since its status code is a permanent redirect.

Considering the resource located at https://example.com as invalid for cache use since the vary headers do not match.

Considering the resource located at https://example.com as valid for cache use since the request is forced to use the cache.

Considering the resource located at https://example.com as needing revalidation since the cache is set to always revalidate.

Considering the resource located at https://example.com as needing revalidation since the response contains the no-cache directive.

Considering the resource located at https://example.com as needing revalidation since the response contains the must-revalidate directive.

Considering the resource located at https://example.com as needing revalidation since the request contains the no-cache directive.

Could not determine the freshness lifetime of the resource located at https://example.com, trying to use heuristics to calculate it.

Successfully calculated the freshness lifetime of the resource located at https://example.com using heuristics.

Could not calculate the freshness lifetime of the resource located at https://example.com. Making a conditional request to revalidate the response.

Considering the resource located at https://example.com as invalid for cache use since the time left for freshness is less than the min-fresh directive.

Considering the resource located at https://example.com as invalid for cache use since the freshness lifetime has been exceeded more than max-stale.

Considering the resource located at https://example.com as valid for cache use since the freshness lifetime has been exceeded less than max-stale.

Considering the resource located at https://example.com as invalid for cache use since the age of the response exceeds the max-age directive.

logs for checking if the response can be cached

Considering the resource located at https://example.com/ as not cachable since its status code (400) is not in the list of cacheable status codes.

Considering the resource located at https://example.com/ as cachable since its status code is a permanent redirect.

Considering the resource located at https://example.com/ as not cachable since the request method (POST) is not in the list of cacheable methods.

Considering the resource located at https://example.com/ as cachable since the request is forced to use the cache.

Considering the resource located at https://example.com/ as not cachable since its status code is informational.

Considering the resource located at https://example.com/ as not cachable since the request contains the no-store directive.

Skipping the no-store directive for the resource located at https://example.com/ since the response contains the must-understand directive.

Considering the resource located at https://example.com/ as not cachable since the response contains the no-store directive.

Considering the resource located at https://example.com/ as not cachable since the response contains the private directive.

Considering the resource located at https://example.com/ as not cachable since it does not contain any of the required cache directives.

Considering the resource located at https://example.com/ as cachable since it meets the criteria for being stored in the cache.

Adding the 'If-Modified-Since' header with the value of 'SOME_DATE to the request for the resource located at https://example.com/.

Adding the 'If-None-Match' header with the value of 'SOME_ETAG' to the request for the resource located at https://example.com/.

[karpetrosyan]

We need to also mention this in the docs