title: Set-Cookie header behaviour in a Preflight OPTIONS request
body: <blockquote>
    <p>Unlike simple requests (discussed above), "preflighted" requests first send an HTTP request by the OPTIONS method to the resource on the other domain, in order to determine whether the actual request is safe to send. </p>
  </blockquote>
  
  <p>(<a href="https://developer.mozilla.org/en-US/docs/Web/HTTP/Access_control_CORS" rel="noreferrer">https://developer.mozilla.org/en-US/docs/Web/HTTP/Access_control_CORS</a>)</p>
  
  <p>Due to CORS, cookies are not being sent along the preflight request. This behaviour is confirmed by that issue. <a href="https://bugs.chromium.org/p/chromium/issues/detail?id=377541" rel="noreferrer">https://bugs.chromium.org/p/chromium/issues/detail?id=377541</a></p>
  
  <p>But what does happen if Set-Cookie is returned in the response? Does the browser remembers that new cookie or simply discards it?</p>