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.

Sign up for GitHub

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

Jump to bottom

Cloudflare timeout errors don't return CORS headers #743

Closed

lukaw3d opened this issue Aug 28, 2024 · 2 comments · Fixed by #849

Assignees

Labels

Member

lukaw3d commented Aug 28, 2024

Related to #733

If nexus doesn't respond, then Cloudflare returns a timeout error, and it is missing CORS headers
(open https://explorer.dev.oasis.io/mainnet/sapphire/address/0x8Bc2B030b299964eEfb5e1e0b36991352E56D2D3/events#events, wait 100 seconds, https://nexus.oasis.io/v1/sapphire/events?limit=10&offset=0&rel=oasis1qpdgv5nv2dhxp4q897cgag6kgnm9qs0dccwnckuu fails with 524, frontend is not allowed to read the error code)

Low priority: it rarely happens, and frontend now does show an error in these cases oasisprotocol/explorer#1513

lukaw3d added the infrastructure label

Member Author

lukaw3d commented Nov 13, 2024

@uscinski says an easy solution is to put a smaller timeout on nexus

ptrus self-assigned this

ptrus mentioned this issue

Return CORS headers also on timeout #849

Merged

Member

ptrus commented Dec 20, 2024

Will be fixed via #821 and #849

ptrus closed this as completed in #849

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment