title: Private vs Public in Cache-Control
body: <p>Can you please describe an example indicating difference between Public and Private Cache-Control in asp.net applications hosted in IIS.</p>
  
  <p>I read in <a href="http://msdn.microsoft.com/en-us/library/system.web.httpcacheability(VS.71).aspx" rel="noreferrer">MSDN</a> that the difference is the following:</p>
  
  <p><strong>Public:</strong> 
  Sets Cache-Control: public to specify that the response is cacheable by clients and shared (proxy) caches.</p>
  
  <p><strong>Private:</strong> Default value. Sets Cache-Control: private to specify that the response is cacheable only on the client and not by shared (proxy server) caches.</p>
  
  <p>I am not sure I have completely understood the pros and cons from each choice. An example for when to or not to use it would be great. </p>
  
  <p>For example what should I do if i have two web servers hosting the same application? Is there anything to watch out if I choose Private or Public?</p>