title: Where do spurious GET calls come from on some networks?
body: <p>Our web app, which has been deployed for a while and gets plenty of traffic, occasionally receives odd requests from the browser.</p>
  <p>I'll have something like:</p>
  <pre><code>axios.post(&quot;/api/endpoint&quot;, {})
  </code></pre>
  <p>in my code and that works pretty regularly.</p>
  <p>For some people, however, the server will get the &quot;POST /api/endpoint&quot; request but then immediately get one or more &quot;GET /api/endpoint&quot;, which will correctly respond with a 404 since it is not POST so this is cluttering up our log files.</p>
  <p>I'm not sure either where this is coming from or what I can do about it.</p>
  <ol>
  <li><p>I don't think there is any way my code can make that GET request but it would be nice to confirm.</p>
  </li>
  <li><p>I assume if axios could do that on some error case or something there would be something in either the docs or the github issues about it, so I doubt that's it.</p>
  </li>
  <li><p>Could it be a browser extension? If so, is there a way to tell?</p>
  </li>
  <li><p>Could it be something in the network configuration? Our customers are on a wide variety of internal networks that can have strange setups. How could I tell? It does seem to be clustered on a few networks, so that seems possible.</p>
  </li>
  <li><p>Could there be a browser behavior that is triggered by a bad network or something or by a misplaced pre-fetch?</p>
  </li>
  </ol>
  <p>We'll probably end up just accepting that route and swallowing it since it doesn't appear to harm anything except our ability to see real errors.</p>
  <p>Thanks!</p>