Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

route "//" does not result in a 404 page nor the index page #11407

Closed
mjarkk opened this issue Mar 27, 2020 · 4 comments · Fixed by #11788
Closed

route "//" does not result in a 404 page nor the index page #11407

mjarkk opened this issue Mar 27, 2020 · 4 comments · Fixed by #11788

Comments

@mjarkk
Copy link

mjarkk commented Mar 27, 2020

Bug report

Describe the bug

When visiting http://localhost:30000// i get a blank page with no error nor any route rendered.

To Reproduce

Steps to reproduce the behavior, please provide code snippets or a repository:

  1. Create a next.js project as described on the website: https://nextjs.org/learn/basics/getting-started/setup
  2. Start the development server using: npm run dev or yarn dev
  3. Visit http://localhost:30000//

Expected behavior

The 404 page

System information

  • OS: Windows
  • Browser: Chrome
  • Version of Next.js: 9.3.2
@mjarkk mjarkk changed the title rout "//" does not result in a 404 page nor the home index page route "//" does not result in a 404 page nor the home index page Mar 27, 2020
@emiliskiskis
Copy link

404 appears for me.

@mjarkk mjarkk changed the title route "//" does not result in a 404 page nor the home index page route "//" does not result in a 404 page nor the index page Mar 27, 2020
@merelinguist
Copy link
Contributor

@timneutkens
Copy link
Member

timneutkens commented Mar 30, 2020

So what seems to happen is that when you go to // it loads up the 404 page (as expected) but does not remove the data-next-hide-fouc bit that prevents a FOUC when using CSS/SCSS imports support.

I can reproduce locally on a simple hello-world when going to http://localhost:3000//

@balazsorban44
Copy link
Member

This issue has been automatically locked due to no recent activity. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.

@vercel vercel locked as resolved and limited conversation to collaborators Jan 30, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants