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

Show error page if the backend is down #51

Open
duncte123 opened this issue Mar 24, 2022 · 5 comments
Open

Show error page if the backend is down #51

duncte123 opened this issue Mar 24, 2022 · 5 comments
Assignees
Labels
bug Something isn't working

Comments

@duncte123
Copy link
Member

Currently, v2 takes ages to load if the backend can't be reached. There should be a quick fail showing an error page saying that Oengus will be back soon.

@duncte123 duncte123 added the bug Something isn't working label Mar 24, 2022
@BobChao87 BobChao87 self-assigned this Mar 24, 2022
@BobChao87
Copy link
Contributor

Some of the API responses can be a little slow however, so what kind of time frame are we thinking? 10 seconds? 15 seconds?

@duncte123
Copy link
Member Author

I would say 30 seconds, but it also needs to take into account the 502 response code and not cache that

@BobChao87
Copy link
Contributor

30, can do. I was thinking maybe a fused timer that pits the API response and just a 30s sleep call against each other to handle that. As for error responses, they should probably be given as the reason for the error instead of the timeout. This shouldn't be too bad to make. And, conveniently, I just taught my local API simulator how to throw errors.

@duncte123
Copy link
Member Author

The 502 does not come from the API, it comes from caddy (the HTTP proxy).

@BobChao87
Copy link
Contributor

Does the system bypass caddy when querying the API from inside of Docker?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants