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

timeouts in our chrome-based prerender service but not prerender.io #9

Open
fool opened this issue Mar 15, 2018 · 6 comments
Open

timeouts in our chrome-based prerender service but not prerender.io #9

fool opened this issue Mar 15, 2018 · 6 comments

Comments

@fool
Copy link
Contributor

fool commented Mar 15, 2018

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.

@verythorough verythorough changed the title timeouts in our chrome-baed prerender service but not prerender.io timeouts in our chrome-based prerender service but not prerender.io Mar 15, 2018
@biilmann
Copy link
Member

Do we know from their logs how long it takes to prerender this URL in prerender.io?

@tommedema
Copy link

See #31, this seems to be affecting us for all our links

@github-actions
Copy link

github-actions bot commented Jun 8, 2021

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!

@github-actions github-actions bot added the stale label Jun 8, 2021
@tommedema
Copy link

still an issue, see also #31

@github-actions github-actions bot removed the stale label Jun 9, 2021
@github-actions
Copy link

github-actions bot commented Jun 9, 2022

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!

@github-actions github-actions bot added the stale label Jun 9, 2022
@tommedema
Copy link

still an issue, see also #31

@github-actions github-actions bot removed the stale label Jun 10, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants