Change Details

## Summary In the event that the proxy is unreachable, or that hCaptcha is unreachable from the proxy, we need a graceful way to automatically fallback to FancyCAPTCHA. In this task, we should discuss options. ## Technical notes ### Option 1 ... ### Option 2 ## Acceptance criteria - [ ] A plan exists for how to automatically fallback to FancyCAPTCHA when needed

## Summary In the event that the proxy is unreachable, or that hCaptcha is unreachable from the proxy, we need a graceful way to automatically fallback to FancyCAPTCHA. In this task, we should discuss options. ## Technical notes ### Option 1 1. in ConfirmEdit `Hooks::getInstance()`, do a request (with a low timeout limit) to the proxy, or to a specific endpoint behind the proxy (e.g. https://docs.hcaptcha.com/#integration-testing-test-keys), if there's no response within the timeout limit, log a message in Logstash, emit an event to Prometheus, and fallback to FancyCAPTCHA. ### Option 2 ... ## Acceptance criteria - [ ] A plan exists for how to automatically fallback to FancyCAPTCHA when needed

## Summary In the event that the proxy is unreachable, or that hCaptcha is unreachable from the proxy, we need a graceful way to automatically fallback to FancyCAPTCHA. In this task, we should discuss options. ## Technical notes ### Option 1 ..1. in ConfirmEdit `Hooks::getInstance()`, do a request (with a low timeout limit) to the proxy, or to a specific endpoint behind the proxy (e.g. https://docs.hcaptcha.com/#integration-testing-test-keys), if there's no response within the timeout limit, log a message in Logstash, emit an event to Prometheus, and fallback to FancyCAPTCHA. ### Option 2 ... ## Acceptance criteria - [ ] A plan exists for how to automatically fallback to FancyCAPTCHA when needed