Bypass instead of Service Auth, right?
BypassService Auth
H
DHDHHHDD
CCCCDCHHHCHHCHCHHCService Auth rules enforce authentication flows that do not require an identity provider IdP login, such as service tokens and mutual TLS.Bypass is if you meet these conditions, skip flow and go back to normal zone security settings
WarningLike if you do bypass on a certain set of IPs
Bypass does not enforce any Access security controls and requests are not logged. This should be tested before deploying to production. Consider using Service Auth if you would like to enforce policies and maintain logging without requiring user authentication.
The Bypass action disables any Access enforcement for traffic that meets the defined rule criteria. This may be useful if you want to ensure your employees have direct permanent access to your internal applications, while still ensuring that any external resource is always asked to authenticate.
When applying a Bypass action, security settings revert to the defaults configured for the zone and any configured page rules. If Always use HTTPS is enabled for the site, then traffic to the bypassed destination continues in HTTPS. If Always use HTTPS is disabled, traffic is HTTP.https://developers.cloudflare.com/cloudflare-one/policies/access/#bypass
H
HHCCCDDDCD
MIA.CDcf.colo.id was a thingD
C
EDCD
KKK
K
curl -v "https://cache-test-behind-access-worker.ai.moda/get-cache"MIAcf.colo.id