Is proxy_cache_bypass recaching?

[Quintin Par]

Can someone help me if this please?

On Tue, Nov 22, 2011 at 8:53 AM, Quintin Par <quintinpar at gmail.com> wrote:

> Hi all,
>
> I have this in my location directive
>
>                     proxy_cache_bypass                     $http_soon;
>
> now I do a curl call to invalidate
>
>
>
> [user at ip-10-111 ~]$ 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
>
>
>
> [user at ip-10-111 ~]$ 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
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nginx.org/pipermail/nginx/attachments/20111123/5c92d717/attachment.html>