Rate limiting - Rate limits are applied based on the request IP.For example, if a request with a Googlebot User Agent has a request IP that's different from Google’s registered IPs, it will be rejected by Cloudflare. Rejection of search engine crawlers and other “good” bots - Cloudflare identifies good bots in part through request IPs and ASNs.This is even more likely if the proxy or CDN alters HTTP headers in some way. Bot management challenges (CAPTCHA) - If all requests come through a single IP or ASN, they're more likely to be identified as bots even if they're legitimate users.However, this is a non-standard use case and may result in undesired behavior, including the following: Zendesk can't prevent customers from configuring their access in this way. Only the proxy communicates directly with Zendesk. The web clients never communicate directly with Zendesk. The reverse proxy intercepts requests from web clients trying to access Zendesk and forwards them to Zendesk. Customers deviating from this standard may experience issues when connecting to Zendesk.įor example, an organization may want their agents and end users to access Zendesk from a single point of access or their own CDN by setting up a reverse proxy. Most Zendesk customers and their customers (end users) access Zendesk directly over the internet. Zendesk has a sophisticated set of abuse protection systems that protect all Zendesk instances and the overall stability of the platform.
0 kommentar(er)
