where is `cf.zone.name` documented again? Trying to see what else I can add
where is
cf.zone.name documented again? Trying to see what else I can add
DThe available fields when setting an HTTP request header value using an expression are the following:
Cyea some are there and not on the overall page, and some aren't on either
Dwhat's the diff between
cf.worker.upstream_zone and cf.zone.nameIdentifies whether a request comes from a worker or not.
When a request comes from a worker, this field will hold the name of the zone for that worker. Otherwise cf.worker.upstream_zone is empty.
Cit should be that if a worker running on cookies.com fetches pineapple.org, and you were running this transform rule/etc on pineapple.org cf.zone.name would be pineapple.org, and upstream_zone would be cookies.com
D'cf.worker.upstream_zone' is not a valid value for expression because the use of field cf.worker.upstream_zone is not allowed (Code: 20087)
Dright, also can't do that lol
Cif you're just looking for useful headers to add, I would add
cf.colo.id <- id of colo, unique for cache
cf.metal.id <- unique metal id in that colo
cf.zone.name
cf.colo.id <- id of colo, unique for cache
cf.metal.id <- unique metal id in that colo
cf.zone.name
Danything else?
CThe convention of adding
x- for custom headers is gone/deprecated and the fact those are uppercase also hurtsCI think you could get the worker via
http.request.headers["cf-worker"][0], not sure if it would be set that point though hmmDwhat's wrong with the uppercase? 
Aren't they converted anyway? I see them as lowercase in my Worker logs
Aren't they converted anyway? I see them as lowercase in my Worker logs
KHTTP/2 lowercases them
Ddoesn't seem to do anything
Care you requesting it via a worker?
Doh
Dno
CI mean that would already be passed to your origin in the cf-worker header anyway if that's a request header rule
DI do the
x- so these headers stand out, and we don't use x- in any of our applications (so this avoids ever having an accidental conflict of header names)CI think you have most of the useful stuff though, you could grab the edge client port for fun if you wanted too
cf.edge.client_port, something you can only get by passing it down.DI'll make them lower case though, good point
Dgood idea, added!
D
Cmetal and colo id can be genuinely helpful at identifying cache stuff
Cwell not really metal, but colo
Dyeah, so for context this is for long term error logging
Dsince Azure support sucks
Kcf.verified_bot_category is cool tooDweird, I got
"x-client-port": "0", on my first attempt
HIs there a
verified_bot_name?Cdid you already have a connection established?
Knop
DD^ example of part of the stuff I'm logging
DI opened one with curl
HDarn
HDo you have to have a dedicated UA, or just not spoof someone else's?
HBecause I feel like I've seen some crawlers with pretty generic UAs
Dyeah, already logging
verifiedBotCategory since I do a json.stringify on the cf request objectHYeah, so if you have IP verify + regex, then you may have two crawlers with similar/same UA, that are differentiated by their IPs, no?
Danything else? 
Dhang on, isn't this pointless since I already log the request headers in my Worker?
CDoh derp
Dis there any situation where it could change or be helpful?
DI'll remove it for now
Deasier to parse without concat'ing, as I'd be worried that that field might be missing.
DI think it's just parsing that I was worried about
Dis there a way to pad http.request.timestamp.msec to include the the first two leading zeros?
Dyeah
