title: ASP.NET Response.Cache.SetNoStore() vs. Response.Cache.SetNoServerCaching()
body: <p>Can anyone break down what these two methods do at a HTTP level.</p>
  
  <p>We are dealing with Akamai edge-caching and have been told that SetNoStore() will cause can exclusion so that (for example) form pages will always post back to the origin server. According to {guy} this sets the HTTP header: </p>
  
  <pre><code>Cache-Control: "no-cache, no-store"
  </code></pre>
  
  <p>As I was implementing this change to our forms I found SetNoServerCaching(). Well that seems to make a bit more sense semantically, and the <a href="http://msdn.microsoft.com/en-us/library/system.web.httpcachepolicy.setnoservercaching%28v=VS.100%29.aspx" rel="noreferrer">documentation</a> says "Explicitly denies caching of the document on the origin-server."</p>
  
  <p>So I went down to the sea sea sea to see what I could see see see. I tried both of these methods and reviewed the headers in Firebug and Fiddler. </p>
  
  <p>And from what I can tell, both these method set the exact same Http Header.</p>
  
  <p>Can anyone explain if there are actual differences between these methods and if so, where are hiding in the http response?!</p>