Support server side redirects

🚀 Feature Proposal

We are using SSR with “authenticated” middleware to protect authenticated routes.

This middleware will check if user is authenticated and if not redirect him to another page, e.g. /login

The logic inside getServerSideProps might look something like this:

export const getServerSideProps: GetServerSideProps<Props> = async (
  context
) => {
  if (someSpecialCase) {
      context.res.writeHead(302, { Location: "/login" });
      context.res.end();
      return undefined;
  }
}

This means that the I would expect /login page to be returned from the getPage function.

[Meemaw]

Yeah, its very high level and abstract, but I think this is the experience most people would expect and would probably suit most of the use cases. I like the fact that there is no implementation details leaked, you don’t even have to know its NextJS underneath.

In theory, library could have multiple “levels” of abstraction and if more fine grained control would be needed some lower level API could be exposed (if there was some use cases for it).

Just thinking out loud: there could be some lower level API exposed that could return more stuff, e.g. page itself + “props”, “redirect”… and it implementation would be used internally by the “higher” level.

// ignore the name. This page would perhaps not be resolved to the redirect automatically but the user would have to do it in code manually
const { page, props, redirect } = await getPageLowerApi({
   route: '/private/page',
});

if(redirect) {
   const { page: redirectedPage } = await getPageLowerApi({ route: redirect })
   render(redirectedPage)
}

[Meemaw]

Totally agree. That is much easier to implement and a way forward 👍

In that case I would just mention somewhere once it is implemented that only those SSR redirects are supported and should be preferred anyway.