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

A fully rendered next page is re-rendered to a 404 page after successfull initial render #868

Closed
sarukuku opened this issue Jan 24, 2017 · 5 comments
Assignees

Comments

@sarukuku
Copy link

I've been trying to track this down for a day now and I've managed to come up with a small example code and I know the version bump that caused this issue.

This happens in older versions of Safari and Mobile Safari. The newest version of Safari I've found to have this issue is version 8.0.8 that is the only bundled browser for Yosemite. It's not even that old comparing how long Mac's last. I haven't seen this bug in other browsers (Chrome, FF etc.) while testing.

In beta.12 the app renders correctly and no issues arise. With beta.13 the app is first rendered correctly and then very quickly re-rendered to a "404 This page could not be found.". I've tracked that the issue is related to next trying to load a URL http://localhost:3000/_next/pages/fi on Safari that leads to a 404 error that causes the app to render the 404 page. Why this is happening is some kind of internal issue with next, custom server and older Safaris (my best guess).

Here's what I can provide to help solve this issue:

@sarukuku
Copy link
Author

sarukuku commented Jan 24, 2017

I know that getting hold of a Safari 8 on Yosemite is a bit tricky but there are free tiers available for browserstack.com that will allow testing this easily.

@tpai
Copy link

tpai commented Jan 24, 2017

Also happening on Safari 9.0.3 and beta.18.

@arunoda arunoda self-assigned this Jan 24, 2017
@arunoda
Copy link
Contributor

arunoda commented Jan 24, 2017

Hmm. It's a bug. Getting that browser is the hardest part.
Let see.

@arunoda
Copy link
Contributor

arunoda commented Jan 24, 2017

Guys, found the issue and here's the fix: #870

@sarukuku
Copy link
Author

Excellent work @arunoda. Hopefully this will make it to the next beta. :)

@lock lock bot locked as resolved and limited conversation to collaborators May 12, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants