Removing `redirects()` from next.config.js does not work

Bug report

Describe the bug

After removing the redirects function from next.config.js, the redirects are still persisting. This should not happen since the redirects have been entirely removed.

To Reproduce

1. Add an initial redirect function in next.config.js:

module.exports = {
    async redirects() {
      return [
        {
          source: '/foo',
          destination: '/bar',
          permanent: true,
        },
      ]
    },
  }

1. Restart the server with yarn dev and see that /foo redirects to /bar.

2. Remove the redirects function

module.exports = {
   
  }

1. Restart the server with yarn dev and see that /foo still redirects to /bar despite the fact that this has been removed.

Expected behavior

The redirect should no longer work after the redirect function has been removed.

System information

• OS: Ubuntu
• Browser: Chrome
• Version of Next.js: v9.5.3
• Version of Node.js: v12.18.3

[ijjk]

Hi, when setting permanent: true on a redirect it uses the 308 status code which instructs the browser to cache the redirect. To skip this cache you should be able to do a hard refresh in your browser. To prevent the redirect from being cached you should use the permanent: false option.

[jonasdehovre]

What did the trick for me was opening the developer tools and in the network tab check the disable cache option 🙌