title: preventing CSFR with Angular client side, .NET webAPI & OWIN authentication
body: <p><a href="https://stackoverflow.com/questions/15574486/angular-against-asp-net-webapi-implement-csrf-on-the-server">This stack overflow question by dbrunning</a> (note - the question itself, not the answers), describes a neat way to merge AngularJS anti-XSRF techniques with a .Net back-end sending out static html (i.e. NOT using cshtml or other format where a token is inserted into the html by the server).</p>
  
  <p>However, it is designed for Microsoft forms authentication.</p>
  
  <p>Given the automatically generated startup.cs and App_Start files which generate when creating a new WebAPI Solution in Visual Studio, How and where would I put something into the OWIN pipeline (neatly) in order to add to the response cookie collection before the page is sent, and remove it on Authentication Sign out. </p>
  
  <p>The application pool is currently .NET 4.6</p>
  
  <p>Thank you.</p>