title: Permanent redirection keeps hitting effective URL everytime
body: <p>I have created two Rest API's in the backend (same webservice), one for the effective URL and other for the Redirected URL. I'm doing a 308 redirection here when user hits effective URL.</p>
  <p>Scenario's</p>
  <ol>
  <li><p>When I mark the API's as POST or PATCH or DELETE,</p>
  <p>In Google chrome, my request always goes to the older url (effective) first and then get's redirected to the other one.</p>
  <p>I had breakpoints in both of the API's and validated that the request always hit's effective first for the above 3 HTTP methods. Also, I have hit the API like 20+ times via Ajax from the browser.</p>
  </li>
  <li><p>When I mark the API's as GET,</p>
  <p>Only the first time, my request goes to the effective url and redirected to the other one. Subsequent call's via the same browser DIRECTLY takes me the other one until I clear the browser cache.</p>
  <p>I suppose this is expected behaviour of permanent redirection (301/308). Also, I'm aware of the difference between 301 and 308.</p>
  </li>
  </ol>
  <p>The major confusion is why the behaviour is not working as intended for NON-GET API's which are POST, PATCH, DELETE etc.</p>
  <p>Chrome browser version: <strong>Version 88.0.4324.192 (Official Build) (x86_64)</strong></p>