fastcgi_cache_key:
work closely with dependencies
fastcgi_cache_key "$request_method|$http_if_modified_since|$http_if_none_match|$host|$request_uri";
Deserves special attention the value in the Directive
fastcgi_cache_key
. I brought the minimum working value for this Directive. Step right, step left, and you will begin in some cases to "wrong" data from the cache. So:
The dependence on $request_method we need, because HEAD-requests to the Internet quite often. Response to a HEAD request never contains body. If you remove the dependence on $request_method, so it may match what someone before you requested the main page of HEAD-method, and you then GET given a blank content.
The dependence on
$http_if_modified_since
need to cache the response 304 Not Modified was not accidentally given to a customer making an ordinary GET request. Otherwise, the client may receive an empty response from the cache.
Same thing with the
$http_if_none_match
. We should be insured from the issuance of blank pages customers!
the dependence on
$host and $request_uri
does not require review
Source:
http://dklab.ru/chicken/nablas/56.html
It seems to me that php script which is responsible for generating the thumbnails simply goes into the cache and more do not want to work. After expiration of the cache or restart the server everything starts working again but goes into the cache and it all starts in a circle. But that's just my opinion.
I would like to know how can I fix this error or to add to iskluchenie, chtoli. - Madison_Dicki commented on October 3rd 19 at 04:17