T
C
M
M
content-type
A
WorkerKVexpiration
C
H
cloudflarenpm i cloudflare
S
CS
HMMMMMMM
.json(body) instead be .json(&body) - ?)M
MFrom the documentation for .json() we can see that it expects a arbitrary serde serializable type. This indicates that what it's doing is creating JSON text from the given value. So, you're sending a JSON-quoted string containing JSON to the server, which is presumably not what it's expecting.… which would describe why you’re likely sending an empty body.
I haven't worked with reqwest, but it looks like for your use case with a JSON string, you would use .body() to provide the string and .header() to specify the JSON Content-Type.
STSSHST
M
CSCNegative lookups indicating that the key does not exist are also cached, so the same delay exists noticing a value is created as when a value is changed.
At the Cloudflare global network location at which changes are made, these changes are usually immediately visible. However, this is not guaranteed and therefore it is not advised to rely on this behaviour. In other global network locations changes may take up to 60 seconds or more to be visible as their cached versions of the data time-out.
Cif I read the key again with cachettl of 30 days would the key come back as null until the 30 days has passed? or would the write be reflected within 60 seconds or so?As for that, with KV 2.0 (or whatever they were calling the new version they announced and then rolled back) it was always doing background refreshes regardless of cache ttl and you'd see changes within ~60s or so, some docs may still reference that. But with KV 1.0, which we are currently on, it's up to cache ttl
V
KVCACHE and re-using in 4-5 workers to cache the basic info using different keys. Is it ok? HVH
C
A
D
DDH
—remoteA
JJC
await this.namespace.put(keyWithPrefix, JSON.stringify(payload), {
expiration: Math.floor(payload.resetTime.getTime() / 1000),
});.json(body).json(&body)KVCACHE—remote