Cloudflare blocking go-http-client User Agent?


Does Cloudflare automatically block the go-http-client user agent?

When I curl an endpoint of mine to imitate the go-http-client, it’s being 403 blocked along the way. I have NO user agent blocks in place and Cloudflare does not seem to have a facility to add ‘allow’ or exceptions to any default blocking.

Bot fight is turned off. Security is turned off, WAF is turned off. Everything under the sun I can think of the might cause it is off! Haha.

< cf-cache-status: DYNAMIC
< cf-request-id: 09a65257360000070e7e11e000000001
< expect-ct: max-age=604800, report-uri=“
< report-to: {“max_age”:604800,“endpoints”:[{“url”:“”}],“group”:“cf-nel”}
< nel: {“report_to”:“cf-nel”,“max_age”:604800}
< server: Cloudflare
< cf-ray: 6450b99ebbb7070e-LHR
< alt-svc: h3-27=“:443”; ma=86400, h3-28=“:443”; ma=86400, h3-29=“:443”; ma=86400

403 Forbidden

Request forbidden by administrative rules. * Connection #0 to host left intact `

That looks like it’s coming from the server. Cloudflare blocks have a Cloudflare block screen. “Administrative Rules” implies it’s a server configuration.

1 Like

This topic was automatically closed 5 days after the last reply. New replies are no longer allowed.