Ive removed the problematic js and redeployed several times
Ive removed the problematic js and redeployed several times
HIve tried refreshing the page with a hard refresh
HThe code being called doesnt exist anymore
C can exist for all request methods
CIt is used more in POST and PUT to tell the server what type of data is being sent json, xml, etc
CTechnically, GET can have a message body, it isn't forbidden by the RFC. But no legitimate request should have a GET body
CMost applications also tend to reject GET requests if they have bodies
Zyou're getting hit by a "workers/pages deployment outage"
HWhere's origin-pull.cloudflare.net ?
Hoh nevermind
HOh thanks, I was going crazy
Dit shouldn't, you should ignore that payload IMO
CTheir free plan seems pretty generous, any catches?
UNot really… 1 user is really the biggest limiting factor
C0.5 TB seems like a lot of data
UIndeed
CI got logpush working with them, seems pretty smooth so far. Thanks for recommending them
COh boy here I go adding another service
CCthey have a CF Worker but not native logpush integration yet it seems. That just adapts the http logpush format and pushes to their API
UYeah they supposedly are working on native logpush not sure when that will happen I assume it’s mostly just convincing CF to add
DIs there an "industry standard" way to print out censored sensitive headers? I was just gonna do or something, but was wondering if there was a "normal" number to do
Dhmm or
KWorkers just does iirc
C
CREDACTED is obvious enough imo, especially on sensitive headers
Dthanks, I'll stick with REDACTED!
DHow can I find out what message ID caused a DMARC rejection?
Dlooks like an IPv6 issue?
Dyeah I think you're right. Super confusing since afaik I did get both emails that were supposedly rejected.
S
DValimail says the same thing too
SShould there be a link?
L
L"CIDR ranges can only be used with 'in' operators"
L
Lhmm
CI mean makes sense. Your source IP isn’t going to be a CIDR range
LYes
LLbots coming to our website from this address are not recognised as verified bots by cloudflare
LWhat's the reason for this?
L
LI solved the problem, the solution is as follows