At the moment, recursive requests to a Deno Deploy instance are blocked. This prevents interesting use cases like allowing an SSR framework to call an internal route, and render the correct content.

Ideally, the same code would work in browser as well as Deno Deploy. Right now, it only works in browser.

Mock code:

```js
const Content = () => {
const { data, error } = useSWR('test', fetcher);
return

{data.title}

const fetcher = () =>
fetch(
`https://my_deno_deploy_url/api/test`,
).then((data) => data.json());
```

This works fine when used locally with the Deno CLI, as well as in the browser (during client side navigation).

But when requesting the route directly from Deno Deploy, I get this error:

`508: Loop Detected (LOOP_DETECTED)\n\nRecursive requests to the same deployment cannot be processed.`

Start by reproducing the mock fetch against a Deno Deploy route, comparing direct requests with local Deno CLI and browser navigation. Done means recursive requests to the same deployment no longer return LOOP_DETECTED while the existing local and browser behavior remains working.

Written by the indexing model from the issue text.