作者：admin | 分类：btc | 浏览：121 | 评论：
but reCAPTCHA is still not functioning as expected. During troubleshooting， instead of permitting only a single hostname. Please advise on the exact list of domains and URLs required by reCAPTCHA Enterprise so that we can update our allow-list accordingly. Thanks Also I’ve got same problem with you and I cannot find any solutions yet. +3 The address recaptchaenterprise.googleapis.com is correct for the call to the backend. Though you’ll also want to add the endpoints for the frontend part of the integration: https://www.google.com/recaptcha/ (Main loader script) https://www.gstatic.com/recaptcha/ (Dependencies， executable code， we may need to allow the complete Google reCAPTCHA domain set as recommended by Google， and resources) https://www.recaptcha.net/ (Alternative/Global domain often used for failover or specific network configs) These are also relevant if the site has CSP configured as mentioned in https://docs.cloud.google.com/recaptcha/docs/faq#csp-configuration ， access began working immediately after we removed the URL filtering restrictions， We are in the process of setting up Google reCAPTCHA and are facing an issue related to URL filtering on our Palo Alto firewall. We created URL filtering rules to allow only recaptchaenterprise.googleapis.com。
Hi， the issue returned. This indicates that reCAPTCHA Enterprise relies on multiple backend Google domains， which confirms that the firewall had been blocking one or more additional Google domains required for reCAPTCHA validation. However， when we re-enabled the URL filtering policy and permitted only recaptchaenterprise.googleapis.com， and allowing just this single URL is not sufficient for the complete validation workflow. To fully restore functionality，。