-
Notifications
You must be signed in to change notification settings - Fork 13
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
timeouts in our chrome-based prerender service but not prerender.io #9
Comments
Do we know from their logs how long it takes to prerender this URL in prerender.io? |
See #31, this seems to be affecting us for all our links |
This issue has been automatically marked as stale because it has not had activity in 1 year. It will be closed in 7 days if no further activity occurs. Thanks! |
still an issue, see also #31 |
This issue has been automatically marked as stale because it has not had activity in 1 year. It will be closed in 7 days if no further activity occurs. Thanks! |
still an issue, see also #31 |
This is a placeholder for the next time we improve the prerender service. Please do not spend any effort on it now until it is reprioritized!
We've seen some URL's that timeout (thus rendering empty on first share) when scraped by facebook via netlify's prerendering that do not similarly timeout on prerender.io. While there is no public statement I can find on this, it seems from others' experiments that taking >10s to prerender causes facebook to give up. Here's one such assertion: prerender/prerender#319 (comment)
Customer report can be found here:
https://netlify.slack.com/archives/C8ZATQKS8/p1521148446000095
...with a URL that exhibits the behavior. At such time as this gets priority, that customer will be happy to create another copy of that URL that we can test with that is not in production use so we can switch back and forth between prerender.io and our prerendering to debug.
The text was updated successfully, but these errors were encountered: