title: Postman and Chrome different API responses
body: <p>I have been making the exact same API request one from postman and one from a react app which is located in localhost so on my machine but when i evaluate the response i get different results between the two.</p>
  
  <p>The request contains odata commands and looks like this:</p>
  
  <pre><code>Articles?$expand=Category&amp;$select=Category
  </code></pre>
  
  <p>The authorization is over a bearer token which i already checked and is correct in both request and the headers and url are the exact same too.</p>
  
  <p>The only thing different is the response where chrome is missing a few entries inside an array which is supposed to contain these Category fields which are Javascript objects.</p>
  
  <p>The response body looks like this:</p>
  
  <pre><code>{
      "@odata.context": ... , value: [
          {
              Category: ...
          }
      ]
  }
  </code></pre>
  
  <p>What is missing is some of the category objects that are there in postman so basically postman is working as intended.</p>
  
  <p>Also for some reason the request appears two times in the network tab one time as OPTIONS and one time as GET which i dont know why either. Somebody good a clue what the culprit could be in this situation?</p>