title: Chrome doesn't attach INGRESSCOOKIE in subsequent requests
body: <p>There are multiple authentication nodes behind load balancer and have sticky session configured to make sure authentication request sent to the same node.</p>
  <p>It only appeared in Chrome, but Firefox worked fine.</p>
  <p>Here is the first request, INGRESSCOOKIE was set in <strong>response</strong> headers
  <img src="https://i.stack.imgur.com/Jow8n.png" alt="This is the first request, INGRESSCOOKIE was set in response headers" /></p>
  <p>Below is the second subsequent request. <code>set-cookie INGRESSCOOKIE</code> was set again in <strong>response</strong> headers, while it's expected to be attached in <strong>request</strong> headers. This appeared in Chrome only
  <a href="https://i.stack.imgur.com/J2Fui.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/J2Fui.png" alt="enter image description here" /></a></p>
  <p>Firefox worked fine without the same issue, below is the second request in Firefox with INGRESSCOOKIE attached in request headers. Any ideas what caused the issue?
  <a href="https://i.stack.imgur.com/u9deO.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/u9deO.png" alt="enter image description here" /></a></p>