fastcgi purge HTTP/1.1 412 Precondition Failed #74
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This option can be slow if a lot of content is cached, or if the storage used for the cache is slow. But you really should be using RAM as your cache storage. Signed-off-by: Francisco Miguel Biete <[email protected]> Signed-off-by: Francisco Miguel Biete <[email protected]> Resolved FRiCKLE#33 Resolved FRiCKLE#35
Put an '*' at the end of your purge cache URL.
e.g:
proxy_cache_key $scheme$host$uri$is_args$args$cookie_JSESSIONID;
curl -X PURGE https://example.com/pass*
This will remove every cached page whose key cache starting with:
httpsexample.com/pass*
Be careful not passing any value for the values after the $uri, or put
it at the end of your cache key.
Signed-off-by: Francisco Miguel Biete <[email protected]>
Signed-off-by: Francisco Miguel Biete <[email protected]>
Resolved FRiCKLE#33
Resolved FRiCKLE#35
cleanup comments a bit
…(html|json|xml|text)
404 can be achieved by using "internal;" https://nginx.org/r/internal
Update status code assertions to match 404 => 412 change, fix root directive in proxy3.t and proxy4.t
Because file.log is not initialized and the file variable is not zeroed out after initialization, the call to ngx_log_error_core in ngx_read_file results in a segmentation fault.
cplcf->conf was not being set when using separate location purge syntax, so the attempt to access cplcf->conf->purge_all in ngx_http_cache_purge_handler was causing a segmentation fault.
Fix tests and segfaults
cache_purge_response_type directive
Dev/fix broken reponse body
Purging multiple cache entries due to the "Vary" request header fails if not specifying the exact same headers in the purge request. This addition supports purging multiple cache entries by adding a "$" at the end of the cache key specified with the purge request.
added support for purging multiple pages with the same cache key
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
8 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
hi
fastcgi_cache_purge PURGE from all;
or
location ~ /purga(/.)?. {
allow all;
fastcgi_cache_purge WORDPRESS "$1mobileversion";
}
curl -X ...............................
HTTP/1.1 412 Precondition Failed
pls help me