Missing HTTP headers
We are currently facing an issue where all HTTP headers, including CF-Connecting-IP, X-Forwarded-For, and CF-IPCountry, are missing from some http requests routed through Cloudflare.
While the majority of traffic includes these headers as expected, a significant number of requests are missing them.
Please assist in reporting this to the Cloudflare team.
17 Replies
I'd make sure all the traffic is from Cloudflare's actual proxy. Cloudflare's ASN is also used for WARP/their VPN, only the ranges on https://www.cloudflare.com/ips/ are used by proxy, and I'd make sure your origin properly only allows those IPs
The traffic is from Cloudflare.
My website is restricted to only be accessed from IPs listed on Cloudflare website.
got any examples of an incoming request like that then? Looking for request headers (censor any ones containing sensitive data of course) + Cf IP
I have many examples with Ray IDs to be investigated by Cloudflare.
I also checked IIS logs to ensure that the headers are missing from the source and not due to an application issue.
@Chaika I am using free plan, so please advise how to share the Ray IDs with Cloudflare team? The issue is still persists and affecting my services.
RAY IDs aren't helpful as far as I am aware, Cloudflare samples super high/doesn't store each request for obvious space reasons.
If this is something that multiple users were reporting and/or if it was reproducible, champs/we can escalate stuff, but would need more info.
You mention you have Ray IDs, so I assume the
cf-ray request header was present?Yes, cf-ray is the only header that is included in http traffic.
What info is needed to escalate? It’s highly urgent.
It'd help to have more information like what I asked above, request headers and requesting ip (cf's ip)
Yes, cf-ray is the only header that is included in http traffic.So it's worth noting just having the CF-Ray header is a configuration you could have caused yourself. In Transform Rules -> Managed Transforms, if you had enabled Remove Visitors IPs and not have Add Visitor Locations on, and you'd have just the cf-ray header and not much else. It's also possible that you would have Modify Request Header Transform Rules stripping these headers off on a more exact match of traffic. If this is just effecting a specific zone/domain it's possible those settings got changed. https://dash.cloudflare.com/?to=/:account/:zone/rules/transform-rules/managed-transforms
The transform rules will affect all http traffic, while the issue I am facing is that some of the traffic is missing CF headers while the majority traffic include all usual headers.
Managed Transforms yes all traffic for that specific zone. Request Header Transform Rules can be much more granular/specific hostnames/pahs/etc
The issue started 10 hours ago while the last configuration update was a year ago.
The traffic for the same hostname/path is received with/without the headers.
I already checked all possible causes and nothing related to the configuration.
Here are some of the IPs:
162.158.86.109
162.158.6.156
162.158.80.155
162.158.80.160
162.158.80.164
162.158.80.165
I also receive traffic from these IPs with the full needed headers such as X-Forwarded-For
Attached are screenshots of a Wireshark capture showing the received traffic from the Cloudflare IP (162.158.6.156).
As you can see, some traffic includes the headers (X-Forwarded-For, X-Forwarded-Proto, CF-Connecting-IP, CF-IPCountry), while other traffic is missing the required headers.
I believe this provides comprehensive details about the issue.
Please help escalating this issue urgently
Hey, could you please send me a repro url? (DM is fine)
@Walshy | Workers/Pages I sent you a message
Thanks but I still need at least one url so i can look at it
also is it still happening? We rolled back something new we were rolling out
@Walshy | Workers/Pages The last noticed one was 30 minutes ago.
I will send url in DM.
Yep looks like it was related to the new software we rolled out
I've let the team know.