Is proxy_cache_bypass recaching?

Hi all,

I have this in my location directive

                proxy_cache_bypass                     $http_soon;

now I do a curl call to invalidate

[[email protected] ~]$ curl “www.site.com/teaser” -I -H “soon:true”

HTTP/1.1 200 OK

Server: nginx

Date: Tue, 22 Nov 2011 03:07:20 GMT

Content-Type: text/html; charset=utf-8

Connection: keep-alive

Keep-Alive: timeout=60

Vary: Accept-Encoding

Vary: Cookie

X-Mod-Pagespeed: 0.9.17.7-716

Cache-Control: max-age=0, no-cache, no-store

X-Cache-Status: BYPASS

[[email protected] ~]$ curl “www.site.com/teaser” -I

HTTP/1.1 200 OK

Server: nginx

Date: Tue, 22 Nov 2011 03:07:37 GMT

Content-Type: text/html; charset=utf-8

Connection: keep-alive

Keep-Alive: timeout=60

Vary: Accept-Encoding

Vary: Cookie

X-Mod-Pagespeed: 0.9.17.7-716

Cache-Control: max-age=0, no-cache, no-store

X-Cache-Status: HIT

Does this mean that the curl call with the header is* recaching the page
and the subsequent hits are cache hits?*

-Quintin

Can someone help me if this please?

Yes. But be aware of Cache-Control header sent by your backend. (
http://wiki.nginx.org/HttpProxyModule#proxy_cache : The cache honors
backend’s “Expires”, “Cache-Control: no-cache”, and “Cache-Control:
max-age=XXX” headers since version 0.7.48. Since version 7.66, “private”
and “no-store” are also honored.)

This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.

| Privacy Policy | Terms of Service | Remote Ruby Jobs