return { redirect: { to: location, status: 301 } } makes no sense

for errors, there’s already a top-level status property. we should use that for redirects as well.

ideas:

return {
  status: 301,
  redirect: '/elsewhere'
};

return {
  status: 301,
  location: '/elsewhere'
};

return {
  redirect: '/elsewhere' // 301 is implicit because 'redirect' exists
};

(We’re already using implicit status codes — it defaults to 200 if no redirect or error — but perhaps explicit is better in this case?)

[Conduitry]

I would tend to not prefer 301 moved permanently as a default for anything because of the caching nightmare.

[Rich-Harris]

closed via #453