title: Any fetch to a url is triggering an additional GET request to it
body: <p>When I fetch with any method (<code>POST</code>, <code>DELETE</code>, etc), on any url, an additional <code>GET</code> request gets triggered on said url. This is a problem in the case of a <code>DELETE /items/:id</code> which followed by a <code>GET /items/:id</code> causes an error because it tries to process the related svelte page with <code>undefined</code> as the input data.</p>
  <p>I tried with several pages and several methods, with <code>console.log</code>s at the beginning of endpoints, this behavior is always the same.</p>
  <p>I have no hook and I don't reload the page after requests. All my <code>fetch</code> calls are contained within functions that can only be called via events on the DOM, so nothing is on the script's root.</p>
  <p>Here's an example of a <code>DELETE</code> endpoint (I'm mainly testing against this one) :</p>
  <pre class="lang-js prettyprint-override"><code>export const DELETE = async ({params}) =&gt; {
    await meta.findOneAndDelete({url: params.url})
    return {}
  }
  </code></pre>
  <p>It even occurs with this :</p>
  <pre class="lang-js prettyprint-override"><code>export const POST = async () =&gt; {
    return {}
  }
  </code></pre>
  <p>I call this endpoint with a <code>fetch(/items/${url}, {method: 'POST'})</code> behind a click event, and it triggers a <code>GET /items/:url</code> everytime. I should point out that these <code>GET</code> requests are not visible in the dev tools, I only see the <code>console.log</code>s I put in the <code>GET</code> endpoints and the potential errors on the server console.</p>