<div dir="ltr">Hi,<br><div><br></div><div>I am following <a href="https://www.ryadel.com/en/nginx-purge-proxy-cache-delete-invalidate-linux-centos-7/">https://www.ryadel.com/en/nginx-purge-proxy-cache-delete-invalidate-linux-centos-7/</a> and <a href="https://bluegrid.io/edu/how-to-purge-the-nginx-cache/">https://bluegrid.io/edu/how-to-purge-the-nginx-cache/</a> to purge cache. I am attaching the nginx file for your reference. </div><div><br></div><div>$curl -I <a href="https://gsmanginxproxycachepurge.testapicraft.com">https://gsmanginxproxycachepurge.testapicraft.com</a> -H "secret-header: true"<br></div><div><br></div><div>HTTP/1.1 200 OK<br>Server: nginx/1.20.2<br>Date: Thu, 28 Apr 2022 19:21:54 GMT<br>Content-Type: text/html; charset=UTF-8<br>Connection: keep-alive<br>Cache-Control: max-age=21600, public<br>Link: <<a href="https://gsmanginxproxycachepurge.testapicraft.com/">https://gsmanginxproxycachepurge.testapicraft.com/</a>>; rel="canonical", <<a href="https://gsmanginxproxycachepurge.testapicraft.com/">https://gsmanginxproxycachepurge.testapicraft.com/</a>>; rel="shortlink", <<a href="https://gsmanginxproxycachepurge.testapicraft.comhome">https://gsmanginxproxycachepurge.testapicraft.comhome</a>>; rel="revision"<br>X-UA-Compatible: IE=edge<br>Content-language: en<br>X-Content-Type-Options: nosniff<br>X-Frame-Options: SAMEORIGIN<br>Permissions-Policy: interest-cohort=()<br>Expires: Sun, 19 Nov 1978 05:00:00 GMT<br>Vary: Cookie<br>X-XSS-Protection: 1; mode=block<br>Strict-Transport-Security: max-age=31536000; includeSubDomains<br>Set-Cookie: ADRUM_BT=R%3A0%7Cg%3A5277dd0a-8de6-440a-a8f7-52fb782db25114%7Cn%3Aicebergtest_e1c60ae6-5d00-47d5-8c0a-690d8465795f%7Ci%3A129601; expires=Thu, 28-Apr-2022 19:14:45 GMT; Max-Age=30; path=/<br>Last-Modified: Tue, 26 Apr 2022 11:42:25 GMT<br>ETag: "1650973345"<br>Access-Control-Allow-Origin: *<br><b>X-Cache-Status: HIT<br></b></div><div><br></div><div>I am seeing it as HIT instead of BYPASS and I am not sure about this term between HIT vs MISS vs BYPASS vs EXPIRED in context to Nginx cache.</div><div><br></div><div>Please guide me. Thanks in advance.</div><div><br></div><div>Best Regards,</div><div><br></div><div>Kaushal</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Apr 27, 2022 at 2:12 AM Sergey A. Osokin <<a href="mailto:osa@freebsd.org.ru">osa@freebsd.org.ru</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hi Kaushal,<br>
<br>
On Tue, Apr 26, 2022 at 11:54:01PM +0530, Kaushal Shriyan wrote:<br>
> Hi Sergey,<br>
> <br>
> I have gone through the document<br>
> <a href="https://docs.nginx.com/nginx/admin-guide/content-cache/content-caching/" rel="noreferrer" target="_blank">https://docs.nginx.com/nginx/admin-guide/content-cache/content-caching/</a> to<br>
> purge nginx cache in nginx OSS version: nginx/1.20.2  as a reverse proxy<br>
> server on CentOS Linux release 7.9.2009 (Core). I encounter<br>
> <br>
> nginx: [emerg] unknown directive "proxy_cache_purge" in<br>
> /etc/nginx/conf.d/default.conf:75<br>
> nginx: [emerg] unknown directive "proxy_cache_purge"<br>
> <br>
> Please guide me. Thanks in advance.<br>
<br>
Accoring to the ngx_http_proxy_module documentation [1], the proxy_cache_purge<br>
directive is available as part of the commercial subscription.<br>
<br>
References:<br>
[1] <a href="https://nginx.org/en/docs/http/ngx_http_proxy_module.html#proxy_cache_purge" rel="noreferrer" target="_blank">https://nginx.org/en/docs/http/ngx_http_proxy_module.html#proxy_cache_purge</a><br>
<br>
-- <br>
Sergey A. Osokin<br>
_______________________________________________<br>
nginx mailing list -- <a href="mailto:nginx@nginx.org" target="_blank">nginx@nginx.org</a><br>
To unsubscribe send an email to <a href="mailto:nginx-leave@nginx.org" target="_blank">nginx-leave@nginx.org</a><br>
</blockquote></div>