H
M
N
I
navigator.sendBeacon
C
I
sendBeacon
BCBCCC
2a06:98c0:3600::103Invalid IP address: >2a06:98c0:3600::103
. It's a decently big international service though, so not sure why we are the only ones hitting it with our WorkersCBCIf I understand correctly, would they need to enable "Pseudo IPv4" on their Cloudflare account then?
CIn cross-zone subrequests from one Cloudflare zone to another Cloudflare zone, the CF-Connecting-IP value will be set to the Worker client IP address '2a06:98c0:3600::103' for security reasons.
BCF-Connecting-IPI see, that's very helpful! So this is an edge case, since we are both using Cloudflare Workers (I'm assuming they are), but they are on a different zone, they get the internal worker IPv6 address in CF-Connecting-IP, even though they don't have IPv6 set up.Yep
If I understand correctly, there is no easy fix for this on both our sides right?I thought about it again and tested it, and Psuedo IPv4 does convert the Worker's IPv6 into a Class-E IPv4, but it's not an easy fix and has a lot of drawbacks of its own. Some legacy systems require IPv4 for fraud reasons or do GeoIP lookups, both of which would fail. Having non-real IPv4s in logging/analytics systems is messy as well if trying to understand/piece together logs or build reports.
CCB
Capi.something.com. And then I set up SaaS hostnames for it. In order to do that, I set up a route */* in order to match all of the requests.other-api.something.com . (Because the */* route is taken). Is that expected?*/*). But that would be ~ 1 route per custom hostname. Is that expected or advisable to write that many routes? */* is a nice solution, but it only works once per Zone. Which means one SaaS worker per zone 
BCBC
LCLLCCLCLCCI have mine set to 1,500 per minute (per key) and I have some cases where I'm seeing 10x that (15k per minute - assumed to be per key)Is the traffic distributed? Rate limiter is per Cloudflare location/pop
CCCC
api.something.com*/**/**/**/*other-api.something.com