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

Can COG detect when a page did not load and retry? #45

Open
gil0109 opened this issue Jul 4, 2018 · 4 comments
Open

Can COG detect when a page did not load and retry? #45

gil0109 opened this issue Jul 4, 2018 · 4 comments
Labels
enhancement New feature or request

Comments

@gil0109
Copy link

gil0109 commented Jul 4, 2018

I would like to startup a webpage using COG, if the page doesn't load or stops loading due to;

  1. Networking issues
  2. Time Server not updated correctly

Is there a flag, to retry or refresh? If not, I can test prior but it would be nice.

@aperezdc aperezdc added the enhancement New feature or request label Jul 5, 2018
@aperezdc
Copy link
Member

aperezdc commented Jul 5, 2018

Sorry, at the moment Cog does not have that option. It can be interesting to add it, though. I can imagine situations where it is better to try reloading that permanently showing the load error page.

Something you can try is using the cogctl tool to remotely trigger a page reload, but there is no way of knowing whether the load succeeded. Probably we could expose the page load status over D-Bus as well.

Another option that you may want to consider is using online and offline events, though I suspect those may not completely solve your use case.

@gil0109
Copy link
Author

gil0109 commented Jul 5, 2018

It would be great to expose the page load status. That way we can script a reload. Thanks for the information.

Also, Sorry I am a new at this. What does this cog option --webprocess-failure do? Is their a possibility to integrate with this?

@EinarArnason
Copy link
Contributor

Can the error page be changed to include a "try again" button at least?

@aperezdc
Copy link
Member

aperezdc commented May 1, 2022

Can the error page be changed to include a "try again" button at least?

Yes, it should be possible, I filed #429 to track that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants