Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have set up my nginx.conf file to use proxy caching from tutorials I have found online. However, I am trying to figure out how to check if it is actually working. I've read somewhere that adding add_header X-Cache-Status $upstream_cache_status; to the config file in the server section should add a caching header to a response that will show if it was from cache (has values of either a HIT, MISS or EXPIRED). However, I'm wondering WHERE I can actually view this header(and its value) as well as if this is the right way/if there is another way. I'm very new to web in general so sorry if this is a noob question. Thanks!

share|improve this question
up vote 4 down vote accepted

You can view headers with

  • the Firefox addon firebug
  • the Chrome debugging console
  • cURL (curl -I <address>)
  • ...
share|improve this answer
Yup curl works, thanks! – still.Learning Oct 4 '12 at 21:12
I'm using nginx as a reverse proxy for my Node server so the headers say nginx in the chrome dev tools, but I'm seeing the GET 200 message show up in the console where I'm running the Node server. Does this mean nginx is not caching? I also checked the cache path and it's empty. – user137717 May 14 at 18:08
That just means, that your browser isn't caching. It doesn't say anything about nginx – Christopher Perrin May 14 at 18:18

Use for example: Enter your site url press "start testing". Sample output:

HTTP/1.1 200 OK
Server: nginx 
Date: Sat, 17 Jan 2015 18:44:25 GMT
Content-Type: text/html; charset=ISO-8859-1
share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.